From: Christoph Egger <Christoph.Egger@amd.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Jinsong Liu <jinsong.liu@intel.com>,
IanCampbell <Ian.Campbell@citrix.com>,
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>,
Will Auld <will.auld@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>,
KeirFraser <keir@xen.org>
Subject: Re: [Xen-devel] [xen vMCE RFC V0.2] xen vMCE design
Date: Tue, 3 Jul 2012 11:45:34 +0200 [thread overview]
Message-ID: <4FF2BF3E.90803@amd.com> (raw)
In-Reply-To: <4FF2B87C020000780008D3E0@nat28.tlf.novell.com>
On 07/03/12 09:16, Jan Beulich wrote:
>>>> On 02.07.12 at 19:32, "Liu, Jinsong" <jinsong.liu@intel.com> wrote:
>> Thanks AMD's feedback :)
>>
>> This vMCE design foils is basically for Intel MCA, involving many details
>> specific to Intel.
>> I agree that for x86 Intel and AMD can share logic in many fields. However,
>> for MCA logic Intel and AMD are quite different, like
>> 1. MSRs interface, e.g. MCG_CAP, MCi_MICS, MCi_CTL2, etc;
>> 2. error injection, AMD provide NMI/single MCE/broadcast MCE, while in our
>> design only concern broadcast MCE# (and pretend to expose CMCI);
>> 3. MCE handler: currently in xen Intel and AMD mce use different triggle
>> method and mce handler;
>>
>> Considering the big difference, I suggest we separately provide Intel vMCE
>> and AMD vMCE (i.e. vmce_intel.c and vmce_amd.c).
>
> I'm not convinced of the need, and would prefer aiming at a
> shared implementation unless issues arise that make this
> impossible.
I have patches ready that do that. About 80% of mce_intel.c is not
Intel specific. I am just waiting for the feature freeze to end...
Christoph
--
---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-07-03 9:45 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 ` [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 [this message]
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=4FF2BF3E.90803@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