From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wei Huang Subject: Re: Re: [PATCH] AMD OSVW (OS Visible Workaround) for Xen Date: Fri, 2 Jul 2010 13:57:50 -0500 Message-ID: <4C2E36AE.5060607@amd.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: "Rosenfeld, Hans" , "'xen-devel@lists.xensource.com'" , Jan Beulich List-Id: xen-devel@lists.xenproject.org Thanks very much. I don't think 4.0.1 needs this patch. -Wei Keir Fraser wrote: > 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 >> >> > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > >