From: Frank Van Der Linden <Frank.Vanderlinden@Sun.COM>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Gavin Maltby <Gavin.Maltby@Sun.COM>,
Christoph Egger <Christoph.Egger@amd.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Ke, Liping" <liping.ke@intel.com>,
"Jiang, Yunhong" <yunhong.jiang@intel.com>
Subject: Re: Re: [RFC] RAS(Part II)--MCA enalbing in XEN
Date: Mon, 16 Feb 2009 22:50:02 -0700 [thread overview]
Message-ID: <499A500A.6000301@Sun.COM> (raw)
In-Reply-To: <4999A94D.5020500@Sun.COM>
I should probably clarify myself, since I may have created one wrong
impression: I don't object to the parts of the Intel code where the
hypervisor does more of the initial work (like is also done in the page
offline code); it can be critical that this work is done quickly, and
the hypervisor is the only place that has both the information and the
means to do it.
So, doing some more work there in some cases is probably the best thing
to do, even though there is natural resistance to adding more code to
the hypervisor.
The main thing that I don't quite understand the benefits of is the vMCE
code, which is why I asked if there are examples of where that approach
would work better.
- Frank
next prev parent reply other threads:[~2009-02-17 5:50 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 5:35 [RFC] RAS(Part II)--MCA enalbing in XEN Ke, Liping
2009-02-16 13:34 ` Christoph Egger
2009-02-16 14:18 ` Christoph Egger
2009-02-16 15:03 ` Keir Fraser
2009-02-16 15:19 ` Jiang, Yunhong
2009-02-16 17:58 ` Frank Van Der Linden
2009-02-17 5:50 ` Frank Van Der Linden [this message]
2009-02-17 6:44 ` Jiang, Yunhong
2009-02-17 6:53 ` Jiang, Yunhong
2009-02-17 6:41 ` Jiang, Yunhong
2009-02-18 18:05 ` Christoph Egger
2009-02-19 9:13 ` Jiang, Yunhong
2009-02-19 16:25 ` Christoph Egger
2009-02-20 2:53 ` Jiang, Yunhong
2009-02-20 21:01 ` Frank van der Linden
2009-02-23 9:01 ` Jiang, Yunhong
2009-02-24 18:53 ` Frank van der Linden
[not found] ` <2E9E6F5F5978EF44A8590E339E888CF988279945@irsmsx503.ger.corp.intel.com>
2009-02-24 19:07 ` Frank van der Linden
[not found] ` <2E9E6F5F5978EF44A8590E339E888CF98827996D@irsmsx503.ger.corp.intel.com>
2009-02-24 20:47 ` Frank van der Linden
2009-02-25 2:25 ` Jiang, Yunhong
2009-02-25 12:19 ` Christoph Egger
2009-02-25 17:32 ` Frank van der Linden
2009-02-26 2:16 ` Jiang, Yunhong
2009-03-02 14:58 ` Christoph Egger
2009-03-02 16:15 ` Jiang, Yunhong
2009-03-02 5:51 ` Jiang, Yunhong
2009-03-02 14:51 ` Christoph Egger
2009-03-02 16:09 ` Jiang, Yunhong
2009-03-02 17:47 ` Frank van der Linden
2009-03-05 4:45 ` Jiang, Yunhong
2009-03-05 8:31 ` Jiang, Yunhong
2009-03-05 14:53 ` Christoph Egger
2009-03-05 15:19 ` Jiang, Yunhong
2009-03-05 17:28 ` Christoph Egger
2009-03-06 2:11 ` Jiang, Yunhong
2009-03-10 1:19 ` Jiang, Yunhong
2009-03-10 19:08 ` Christoph Egger
2009-03-12 15:52 ` Jiang, Yunhong
2009-03-16 16:27 ` Frank van der Linden
2009-02-25 22:30 ` Gavin Maltby
2009-02-25 2:31 ` Jiang, Yunhong
2009-02-25 10:57 ` Christoph Egger
2009-02-25 2:26 ` Jiang, Yunhong
2009-02-25 10:37 ` Christoph Egger
2009-02-16 15:05 ` 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=499A500A.6000301@Sun.COM \
--to=frank.vanderlinden@sun.com \
--cc=Christoph.Egger@amd.com \
--cc=Gavin.Maltby@Sun.COM \
--cc=keir.fraser@eu.citrix.com \
--cc=liping.ke@intel.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 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.