From: Frank van der Linden <Frank.Vanderlinden@Sun.COM>
To: "Kleen, Andi" <andi.kleen@intel.com>
Cc: Christoph Egger <Christoph.Egger@amd.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Jiang, Yunhong" <yunhong.jiang@intel.com>,
"Ke, Liping" <liping.ke@intel.com>,
Gavin Maltby <Gavin.Maltby@Sun.COM>,
Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: Re: [RFC] RAS(Part II)--MCA enalbing in XEN
Date: Tue, 24 Feb 2009 12:07:16 -0700 [thread overview]
Message-ID: <49A44564.3080505@Sun.COM> (raw)
In-Reply-To: <2E9E6F5F5978EF44A8590E339E888CF988279945@irsmsx503.ger.corp.intel.com>
Kleen, Andi wrote:
>> MCA information is highly specific to the hardware.
>
> Actually Intel has architectural machine checks and except for
> some optional addon information explicitely marked it's all architectural
> (as in defined to stay the same going forward)
True, I probably expressed myself poorly here. I meant to say: it's a
physical hardware error, and in an unmodified virtualized environment
the information about the physical hardware isn't there.
> For DomU translation of the address is needed, that's correct.
> For Dom0 logging physical is good because the logging tools
> might need that.
Right. As far as I understand it, this patch proposes to deliver the
actual physical information to dom0 via the existing vIRQ mechanism,
while the vMCE mechanism delivers virtualized info to any guest (both
dom0 and domU).
- Frank
next prev parent reply other threads:[~2009-02-24 19:07 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
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 [this message]
2009-02-25 2:26 ` Jiang, Yunhong
2009-02-25 10:37 ` Christoph Egger
[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-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=49A44564.3080505@Sun.COM \
--to=frank.vanderlinden@sun.com \
--cc=Christoph.Egger@amd.com \
--cc=Gavin.Maltby@Sun.COM \
--cc=andi.kleen@intel.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.