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>,
"JBeulich@suse.com" <JBeulich@suse.com>
Subject: Re: [PATCH V3] X86/vMCE: handle broken page with regard to migration
Date: Tue, 20 Nov 2012 17:23:18 +0000 [thread overview]
Message-ID: <50ABBC86.6040701@eu.citrix.com> (raw)
In-Reply-To: <DE8DF0795D48FD4CA783C40EC8292335393633@SHSMSX101.ccr.corp.intel.com>
On 20/11/12 17:08, Liu, Jinsong wrote:
>> On the other hand, the whole situation is hopefully rare enough that
>> maybe we can just do the simple correct thing, even if it's a tiny bit
>> sub-optimal. In that case, assuming that spurious vMCEs aren't a
>> problem (e.g., #1), I think we basically just need to see if the last
>> iteration contains a broken page, and if so, send the guest a vMCE on
>> resume.
>>
>> Thoughts?
>
> Yes, that's exactly V3 patch did.
Right -- but you did it by adding an extra couple of loops, which made
us wonder if there was a more efficient way to do the same thing. Now
that we know *what* needs to be done, we're in a better position to
think about other options. Let me take a look...
-George
next prev parent reply other threads:[~2012-11-20 17:23 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-17 2:04 [PATCH V3] X86/vMCE: handle broken page with regard to migration Liu Jinsong
2012-11-16 18:19 ` Ian Jackson
2012-11-16 18:31 ` Liu, Jinsong
2012-11-19 9:55 ` Ian Campbell
2012-11-19 15:29 ` George Dunlap
2012-11-19 16:57 ` Ian Campbell
2012-11-20 15:08 ` George Dunlap
2012-11-20 17:08 ` Liu, Jinsong
2012-11-20 17:23 ` George Dunlap [this message]
2012-11-20 17:49 ` Liu, Jinsong
2012-11-20 18:54 ` Liu, Jinsong
2012-11-21 11:07 ` Ian Campbell
2012-11-21 11:18 ` George Dunlap
2012-11-21 12:11 ` Liu, Jinsong
2012-11-20 16:43 ` Liu, Jinsong
2012-11-20 16:29 ` Liu, Jinsong
2012-11-20 16:11 ` Liu, Jinsong
2012-11-20 17:48 ` George Dunlap
2012-11-20 18:13 ` Liu, Jinsong
2012-11-20 18:21 ` Ian Jackson
2012-11-20 18:39 ` Liu, Jinsong
2012-11-20 18:42 ` Ian Jackson
2012-11-20 19:07 ` Liu, Jinsong
2012-11-21 11:34 ` George Dunlap
2012-11-21 11:55 ` Ian Jackson
2012-11-21 12:11 ` Ian Campbell
2012-11-21 12:15 ` George Dunlap
2012-11-21 13:26 ` Liu, Jinsong
2012-11-21 13:37 ` Jan Beulich
2012-11-22 11:23 ` Liu, Jinsong
2012-11-21 13:59 ` George Dunlap
2012-11-22 11:44 ` Liu, Jinsong
2012-11-21 12:17 ` George Dunlap
2012-11-21 13:31 ` Liu, Jinsong
2012-11-22 12:37 ` Liu, Jinsong
2012-11-22 13:36 ` Jan Beulich
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=50ABBC86.6040701@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.