xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>,
	Tim Deegan <Tim.Deegan@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: RE: [PATCH] Don't enable irq for machine check vmexit
Date: Fri, 05 Feb 2010 14:59:05 +0000	[thread overview]
Message-ID: <C791E2B9.93C7%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <C8EDE645B81E5141A8C6B2F73FD9265118FED93B52@shzsmsx501.ccr.corp.intel.com>

On 05/02/2010 14:36, "Jiang, Yunhong" <yunhong.jiang@intel.com> wrote:

>> How about the attached alternative, which avoids repeated reads of
>> VM_INTR_INFO? Also I'm not sure whether checking for
>> VM_EXIT_REASONS_FAILED_VMENTRY is useful, so I removed it. After all,
>> EXIT_REASON_MCE_DURING_VMENTRY should imply it anyway.
> 
> Thanks for your patch. Yes, it is much better to avoid the repeated read.
> 
> I'm not sure if it is ok if we don't check the VM_EXIT_REASONS_FAILED_VMENTRY.
> Checking the SDM and seems it is ok. In fact, I didn't find effective method
> to test this VMEntry MCE failed case, althgouh I can test MCE VMExit with
> EXIT_REASON_EXCEPTION_NMI case easily. (I will try to find a method to test
> this VMEntry failure case next week, maybe poison the VMCS range can trigger
> it, I'm not sure).

Well, we don't seem to know what bit 31 is for. Or, at least, we don't know
how it should affect our behaviour in the vmexit handler. So looking at it
does seem a bit pointless.

 -- Keir

  reply	other threads:[~2010-02-05 14:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-01  9:18 [PATCH] Don't enable irq for machine check vmexit Jiang, Yunhong
2010-02-01 11:14 ` Keir Fraser
2010-02-04  9:26 ` Jiang, Yunhong
2010-02-04 10:03   ` Keir Fraser
2010-02-04 12:25     ` Jiang, Yunhong
2010-02-04 14:21       ` Tim Deegan
2010-02-04 14:35         ` Jiang, Yunhong
2010-02-05 10:22         ` Jiang, Yunhong
2010-02-05 10:42           ` Tim Deegan
2010-02-05 14:37             ` Jiang, Yunhong
2010-02-05 12:53           ` Keir Fraser
2010-02-05 14:36             ` Jiang, Yunhong
2010-02-05 14:59               ` Keir Fraser [this message]
2010-02-07  4:25                 ` Jiang, Yunhong

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=C791E2B9.93C7%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=Tim.Deegan@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yunhong.jiang@intel.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).