From: Christoph Egger <Christoph.Egger@amd.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Tony Luck <tony.luck@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>,
Jinsong Liu <jinsong.liu@intel.com>,
Jun Nakajima <jun.nakajima@intel.com>,
Susie Li <susie.li@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 17:33:29 +0200 [thread overview]
Message-ID: <4FF310C9.9040108@amd.com> (raw)
In-Reply-To: <4FF3270C020000780008D5A9@nat28.tlf.novell.com>
On 07/03/12 17:08, Jan Beulich wrote:
>>>> On 03.07.12 at 16:50, Christoph Egger <Christoph.Egger@amd.com> wrote:
>> On 07/03/12 15:26, Luck, Tony wrote:
>>
>>>> I'm not convinced of the need, and would prefer aiming at a
>>>> shared implementation unless issues arise that make this
>>>> impossible.
>>>
>>> It does sound odd. Yes, Intel and AMD have differences around CMCI ... but
>> we are never
>>> going to send a CMCI to a guest (there is no point, it can't do anything
>> useful with the
>>> information, it may do something pointlessly stupid like stop using a guest
>> physical page).
>>> The only reason I suggested making MCG_CAP pretend that CMCI was supported
>> was a
>>> small optimization ... if a Linux guest sees that CMCI is supported, it will
>> not poll the machine
>>> check banks looking for corrected errors.
>>
>>
>> Are you talking about PV or HVM guest?
>>
>> For HVM guests yes it makes sense to disable CMCI in MCG_CAP for both
>> AMD and Intel.
>
> "enable" you mean?
Oh, sorry. I misread one sentence.
If CMCI for the guest is really just emulated (= 100% software)
then yes, enable for both AMD and Intel is fine.
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
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Egger <Christoph.Egger@amd.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Tony Luck <tony.luck@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>,
Jinsong Liu <jinsong.liu@intel.com>,
Jun Nakajima <jun.nakajima@intel.com>,
Susie Li <susie.li@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 17:33:29 +0200 [thread overview]
Message-ID: <4FF310C9.9040108@amd.com> (raw)
In-Reply-To: <4FF3270C020000780008D5A9@nat28.tlf.novell.com>
On 07/03/12 17:08, Jan Beulich wrote:
>>>> On 03.07.12 at 16:50, Christoph Egger <Christoph.Egger@amd.com> wrote:
>> On 07/03/12 15:26, Luck, Tony wrote:
>>
>>>> I'm not convinced of the need, and would prefer aiming at a
>>>> shared implementation unless issues arise that make this
>>>> impossible.
>>>
>>> It does sound odd. Yes, Intel and AMD have differences around CMCI ... but
>> we are never
>>> going to send a CMCI to a guest (there is no point, it can't do anything
>> useful with the
>>> information, it may do something pointlessly stupid like stop using a guest
>> physical page).
>>> The only reason I suggested making MCG_CAP pretend that CMCI was supported
>> was a
>>> small optimization ... if a Linux guest sees that CMCI is supported, it will
>> not poll the machine
>>> check banks looking for corrected errors.
>>
>>
>> Are you talking about PV or HVM guest?
>>
>> For HVM guests yes it makes sense to disable CMCI in MCG_CAP for both
>> AMD and Intel.
>
> "enable" you mean?
Oh, sorry. I misread one sentence.
If CMCI for the guest is really just emulated (= 100% software)
then yes, enable for both AMD and Intel is fine.
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 15:32 UTC|newest]
Thread overview: 20+ 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
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:19 ` Auld, Will
2012-07-03 15:33 ` Christoph Egger [this message]
2012-07-03 15:33 ` [Xen-devel] " 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=4FF310C9.9040108@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 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.