From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] AMD OSVW (OS Visible Workaround) for Xen Date: Fri, 2 Jul 2010 19:05:45 +0100 Message-ID: References: <4C2CE9BD.40603@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C2CE9BD.40603@amd.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Wei Huang , Jan Beulich , "'xen-devel@lists.xensource.com'" , Hans Rosenfeld List-Id: xen-devel@lists.xenproject.org On 01/07/2010 20:17, "Wei Huang" 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... -- Keir > Signed-off-by: Wei Huang > Signed-off-by: Hans Rosenfeld > Acked-by: Jan Beulich >