From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: RE: Re: [PATCH] AMD OSVW (OS Visible Workaround) for Xen Date: Mon, 05 Jul 2010 15:54:49 +0100 Message-ID: <4C320E5902000078000098D6@vpn.id2.novell.com> References: <4C2E36AE.5060607@amd.com>, <4C31A1BE02000078000097A5@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline 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 Huang2 , Keir Fraser Cc: Hans Rosenfeld , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org >>> On 05.07.10 at 16:23, "Huang2, Wei" wrote: > My thought was that this patch won't affect newer families of CPUs = (i.e.=20 > production parts). I expected this erratum will be fixed on them. But if = you=20 If you know that's going to be the case, then I agree. > disagree, I will ask Keir to apply it to Xen 4.0.1.=20 Jan