RE: [Xen-devel] Re: [PATCH] AMD OSVW (OS Visible Workaround) for Xen

["Huang2, Wei" <Wei.Huang2@xxxxxxx>]

Hi Jan,

My thought was that this patch won't affect newer families of CPUs (i.e. 
production parts). I expected this erratum will be fixed on them. But if you 
disagree, I will ask Keir to apply it to Xen 4.0.1. 

Thanks,
-Wei
________________________________________
From: Jan Beulich [JBeulich@xxxxxxxxxx]
Sent: Monday, July 05, 2010 2:11 AM
To: Huang2, Wei; Keir Fraser
Cc: Rosenfeld, Hans; xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Re: [PATCH] AMD OSVW (OS Visible Workaround)    for Xen

>>> On 02.07.10 at 20:57, Wei Huang <wei.huang2@xxxxxxx> 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@xxxxxxx> 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




_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel