From: George Dunlap <george.dunlap@eu.citrix.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH V4] X86/vMCE: handle broken page with regard to migration
Date: Mon, 3 Dec 2012 11:24:07 +0000 [thread overview]
Message-ID: <50BC8BD7.3020908@eu.citrix.com> (raw)
In-Reply-To: <DE8DF0795D48FD4CA783C40EC829233539B85D@SHSMSX101.ccr.corp.intel.com>
On 30/11/12 18:51, Liu, Jinsong wrote:
>
> Not exactly I think. Reading the broken page will trigger a serious SRAR error. Under such case hypervisor will inject a vMCE to the guest which was migrating, not dom0. The reason of this injection is, guest is best one to handle it, w/ sufficient clue/status/information (other component like hypervisor/dom0 are not proper). For xl migration process, after return from MCE context, it *again* read the broken page ... this will kill system entirely --> so we definitely not care migration any more.
Why would the vMCE be sent to the guest, rather than the vcpu that was
running when the SRAR error occured (i.e., the vcpu on which the
migration process was running)?
-George
next prev parent reply other threads:[~2012-12-03 11:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 0:25 [PATCH V4] X86/vMCE: handle broken page with regard to migration Liu Jinsong
2012-11-23 16:26 ` George Dunlap
2012-11-25 13:24 ` Liu, Jinsong
2012-11-28 14:37 ` Liu, Jinsong
2012-11-29 10:02 ` Ian Campbell
2012-11-29 10:50 ` George Dunlap
2012-11-30 18:57 ` Liu, Jinsong
2012-11-30 18:51 ` Liu, Jinsong
2012-12-03 11:24 ` George Dunlap [this message]
2012-12-05 15:57 ` Liu, Jinsong
2012-12-05 15:59 ` George Dunlap
2012-12-05 16:36 ` Liu, Jinsong
2012-12-05 16:01 ` Ian Campbell
2012-12-05 16:15 ` Liu, Jinsong
-- strict thread matches above, loose matches on Subject: below --
2012-11-23 0:13 Liu Jinsong
2012-11-22 16:28 ` Liu, Jinsong
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=50BC8BD7.3020908@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=jinsong.liu@intel.com \
--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).