From: Christoph Egger <Christoph.Egger@amd.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>
Cc: Jan Beulich <JBeulich@suse.com>,
"Auld, Will" <will.auld@intel.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
"Luck, Tony" <tony.luck@intel.com>, Keir Fraser <keir@xen.org>,
"Raj, Ashok" <ashok.raj@intel.com>,
"Jiang, Yunhong" <yunhong.jiang@intel.com>,
"Li, Susie" <susie.li@intel.com>,
"Shan, Haitao" <haitao.shan@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Dugger, Donald D" <donald.d.dugger@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
"Zhang, Xiantao" <xiantao.zhang@intel.com>
Subject: Re: [Xen-devel] [xen vMCE RFC V0.2] xen vMCE design
Date: Fri, 29 Jun 2012 11:58:55 +0200 [thread overview]
Message-ID: <4FED7C5F.1040908@amd.com> (raw)
In-Reply-To: <DE8DF0795D48FD4CA783C40EC8292335265284@SHSMSX101.ccr.corp.intel.com>
Feedback from the AMD side:
slide 2:
- PV guests are supposed to install a MCE trap handler
which reads the MSR values from struct mcinfo_bank.
Hence it is unclear where the #GP should come from.
Same for HVM guests which have a PV MCE "driver"
(those are very rare in reality).
slide 3:
- unclear what "Weird per-domain MSRs" means
- unclear what "Unnatural MCE injection semantics" means
slide 4:
- typo: interace -> interface :-)
- enable UCR-related capabilities, but only on Intel machines
- Filter non-SRAO/SRAR banks:
Rename it to "Let guest see northbridge bank only to the guest"
slide 7:
- ignore/disable CMCI and CTL2 on AMD
slide 8:
- Filter non-SRAO/SRAR banks:
Rename it to "Let guest see northbridge bank only to the guest"
- Question: Should we allow the guest to inject errors? Does it make
sense?
- always disable MCi_CTL2 on AMD
slide 9:
- Model specific issue: Also affects AMD as some models have
l3 cache and some do not.
E.g. it does not make sense to report l3 cache errors to guests
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85689 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2012-06-29 9:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 3:51 [xen vMCE RFC V0.2] xen vMCE design Liu, Jinsong
2012-06-27 13:14 ` Jan Beulich
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 ` Christoph Egger [this message]
2012-07-02 17:32 ` [Xen-devel] " 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=4FED7C5F.1040908@amd.com \
--to=christoph.egger@amd.com \
--cc=Ian.Campbell@citrix.com \
--cc=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