From: "Jan Beulich" <JBeulich@novell.com>
To: Wei Huang <wei.huang2@amd.com>, Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Hans Rosenfeld <Hans.Rosenfeld@amd.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: [PATCH] AMD OSVW (OS Visible Workaround) for Xen
Date: Mon, 05 Jul 2010 08:11:26 +0100 [thread overview]
Message-ID: <4C31A1BE02000078000097A5@vpn.id2.novell.com> (raw)
In-Reply-To: <4C2E36AE.5060607@amd.com>
>>> On 02.07.10 at 20:57, Wei Huang <wei.huang2@amd.com> wrote:
> Thanks very much. I don't think 4.0.1 needs this patch.
I was about to reply with the opposite statement - why do you think
so?
> Keir Fraser wrote:
>> On 01/07/2010 20:17, "Wei Huang" <wei.huang2@amd.com> wrote:
>>
>>
>>> This path enables AMD OSVW (OS Visible Workaround) feature for Xen. New
>>> AMD errata will have a OSVW id assigned in the future. OS is supposed to
>>> check OSVW status MSR to find out whether CPU has a specific erratum.
>>> Legacy errata are also supported in this patch: traditional
>>> family/model/stepping approach will be used if OSVW feature isn't
>>> applicable. This patch is adapted from Hans Rosenfeld's patch submitted
>>> to Linux kernel .
>>>
>>
>> Applied to xen-unstable. Is this for 4.0.1 also? It is a big patch and it
>> doesn't say it actually fixes any issues...
It's big only because of it moving around amd.h...
The issue it fixes is that newer AMD processor families apparently
also require the workaround for erratum 383 (previously applied to
Fam10 only).
Jan
next prev parent reply other threads:[~2010-07-05 7:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 19:17 [PATCH] AMD OSVW (OS Visible Workaround) for Xen Wei Huang
2010-07-02 18:05 ` Keir Fraser
2010-07-02 18:57 ` Wei Huang
2010-07-05 7:11 ` Jan Beulich [this message]
2010-07-05 14:23 ` Huang2, Wei
2010-07-05 14:54 ` Jan Beulich
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=4C31A1BE02000078000097A5@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=Hans.Rosenfeld@amd.com \
--cc=keir.fraser@eu.citrix.com \
--cc=wei.huang2@amd.com \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).