[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] vmx: Make it clear that the VMEXIT reason is in hex


  • To: Tim Deegan <tim@xxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxx>
  • Date: Thu, 15 Mar 2012 10:29:47 +0000
  • Delivery-date: Thu, 15 Mar 2012 10:30:09 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: Ac0ClotbiiwK/+MjKkKx7Bi7Lg9fOw==
  • Thread-topic: [Xen-devel] [PATCH] vmx: Make it clear that the VMEXIT reason is in hex

On 15/03/2012 10:14, "Tim Deegan" <tim@xxxxxxx> wrote:

> # HG changeset patch
> # User Tim Deegan <tim@xxxxxxx>
> # Date 1331806143 0
> # Node ID ab772600a1ed6d889e8bdf55f49ba75123031a3e
> # Parent  c25ec9e9a8126d562d2a72620aea8ee6b104f89e
> vmx: Make it clear that the VMEXIT reason is in hex.
> 
> Signed-off-by: Tim Deegan <tim@xxxxxxx>

Acked-by: Keir Fraser <keir@xxxxxxx>

> diff -r c25ec9e9a812 -r ab772600a1ed xen/arch/x86/hvm/vmx/vmx.c
> --- a/xen/arch/x86/hvm/vmx/vmx.c Wed Mar 14 14:20:58 2012 +0000
> +++ b/xen/arch/x86/hvm/vmx/vmx.c Thu Mar 15 10:09:03 2012 +0000
> @@ -2720,7 +2720,7 @@ void vmx_vmexit_handler(struct cpu_user_
>      /* fall through */
>      default:
>      exit_and_crash:
> -        gdprintk(XENLOG_ERR, "Bad vmexit (reason %x)\n", exit_reason);
> +        gdprintk(XENLOG_ERR, "Bad vmexit (reason %#x)\n", exit_reason);
>          domain_crash(v->domain);
>          break;
>      }
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.