From: Gavin Maltby <Gavin.Maltby@Sun.COM>
To: Christoph Egger <Christoph.Egger@amd.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Jiang, Yunhong" <yunhong.jiang@intel.com>,
"Ke, Liping" <liping.ke@intel.com>,
"Frank.Vanderlinden@Sun.COM" <Frank.Vanderlinden@Sun.COM>,
Keir Fraser <keir.fraser@eu.citrix.com>,
"Kleen, Andi" <andi.kleen@intel.com>
Subject: Re: Re: [RFC] RAS(Part II)--MCA enalbing in XEN
Date: Thu, 26 Feb 2009 09:30:32 +1100 [thread overview]
Message-ID: <49A5C688.1070001@sun.com> (raw)
In-Reply-To: <200902251319.29299.Christoph.Egger@amd.com>
Christoph Egger wrote:
> Mostly. Regarding 2) I want like to discuss first how to handle errors
> impacting multiple contiguous physical pages which are non-contigous
> in guest physical space.
I can't think of any such error types. ECC checkwords don't span
page boundaries, so you only ever get an error at a time
affecting one small part of one page. That physically adjacent
pages have both had errors would come our in the wash, but
they'd be processed and recognised individually.
Gavin
next prev parent reply other threads:[~2009-02-25 22:30 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
2009-02-25 2:26 ` Jiang, Yunhong
[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 [this message]
2009-02-25 2:31 ` Jiang, Yunhong
2009-02-25 10:57 ` Christoph Egger
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=49A5C688.1070001@sun.com \
--to=gavin.maltby@sun.com \
--cc=Christoph.Egger@amd.com \
--cc=Frank.Vanderlinden@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.