xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xen.org>
To: Tim Deegan <tim@xen.org>, xen-devel@lists.xensource.com
Subject: Re: [PATCH] vmx: Make it clear that the VMEXIT reason is in hex
Date: Thu, 15 Mar 2012 10:29:47 +0000	[thread overview]
Message-ID: <CB87751B.3BA50%keir@xen.org> (raw)
In-Reply-To: <ab772600a1ed6d889e8b.1331806458@whitby.uk.xensource.com>

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

> # HG changeset patch
> # User Tim Deegan <tim@xen.org>
> # 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@xen.org>

Acked-by: Keir Fraser <keir@xen.org>

> 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@lists.xen.org
> http://lists.xen.org/xen-devel

      reply	other threads:[~2012-03-15 10:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15 10:14 [PATCH] vmx: Make it clear that the VMEXIT reason is in hex Tim Deegan
2012-03-15 10:29 ` Keir Fraser [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CB87751B.3BA50%keir@xen.org \
    --to=keir@xen.org \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).