From: "Jan Beulich" <JBeulich@suse.com>
To: "Jinsong Liu" <jinsong.liu@intel.com>, "Will Auld" <will.auld@intel.com>
Cc: "Ashok Raj" <ashok.raj@intel.com>,
"Donald D Dugger" <donald.d.dugger@intel.com>,
"Haitao Shan" <haitao.shan@intel.com>,
"Jun Nakajima" <jun.nakajima@intel.com>,
"Susie Li" <susie.li@intel.com>,
"Tony Luck" <tony.luck@intel.com>,
"Xiantao Zhang" <xiantao.zhang@intel.com>,
"Yunhong Jiang" <yunhong.jiang@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Keir Fraser" <keir@xen.org>
Subject: Re: [xen vMCE RFC V0.2] xen vMCE design
Date: Wed, 27 Jun 2012 14:14:52 +0100 [thread overview]
Message-ID: <4FEB236C020000780008C392@nat28.tlf.novell.com> (raw)
In-Reply-To: <DE8DF0795D48FD4CA783C40EC829233525D395@SHSMSX101.ccr.corp.intel.com>
>>> On 27.06.12 at 05:51, "Liu, Jinsong" <jinsong.liu@intel.com> wrote:
> This is updated xen vMCE design foils, according to comments from community
> recently.
>
> This foils focus on vMCE part of Xen MCA, so as Keir said, it's some dense.
> Later Will will present a document to elaborate more, including Intel MCA
> and surrounding features and Xen implementation.
For MCi_CTL2 you probably meant to say "allow setting CMCI_EN
and error count threshold"?
The 2-bank approach also needs to be brought in line with the
current host derived value in MCG_CAP, especially if the code to
implement this new model doesn't make it into 4.2 (which would
generally save a larger value).
Jan
next prev parent reply other threads:[~2012-06-27 13:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 3:51 Liu, Jinsong
2012-06-27 13:14 ` Jan Beulich [this message]
2012-06-28 8:54 ` Liu, Jinsong
2012-06-28 9:08 ` Jan Beulich
2012-06-28 9:40 ` Liu, Jinsong
2012-06-28 9:55 ` Jan Beulich
2012-06-28 9:58 ` [Xen-devel] " Ian Campbell
2012-06-28 13:38 ` Liu, Jinsong
2012-06-28 14:00 ` Jan Beulich
2012-06-28 17:02 ` Liu, Jinsong
2012-06-29 9:58 ` [Xen-devel] " Christoph Egger
2012-07-02 17:32 ` Liu, Jinsong
2012-07-03 7:16 ` Jan Beulich
2012-07-03 9:45 ` Christoph Egger
2012-07-03 13:26 ` Luck, Tony
2012-07-03 14:50 ` Christoph Egger
2012-07-03 15:08 ` Jan Beulich
2012-07-03 15:33 ` Christoph Egger
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=4FEB236C020000780008C392@nat28.tlf.novell.com \
--to=jbeulich@suse.com \
--cc=ashok.raj@intel.com \
--cc=donald.d.dugger@intel.com \
--cc=haitao.shan@intel.com \
--cc=jinsong.liu@intel.com \
--cc=jun.nakajima@intel.com \
--cc=keir@xen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=susie.li@intel.com \
--cc=tony.luck@intel.com \
--cc=will.auld@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=xiantao.zhang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®