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

To:	"Wei Huang2" <Wei.Huang2@xxxxxxx>, "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>
Subject:	RE: [Xen-devel] Re: [PATCH] AMD OSVW (OS Visible Workaround) for Xen
From:	"Jan Beulich" <JBeulich@xxxxxxxxxx>
Date:	Mon, 05 Jul 2010 15:54:49 +0100
Cc:	Hans Rosenfeld <Hans.Rosenfeld@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date:	Mon, 05 Jul 2010 07:56:12 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<EE335F95F28A664DB4A21289D2AA053B42E7D16D@xxxxxxxxxxxxxxxxxxx>
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References:	<C853E909.19508%keir.fraser@xxxxxxxxxxxxx> <4C2E36AE.5060607@xxxxxxx>, <4C31A1BE02000078000097A5@xxxxxxxxxxxxxxxxxx> <EE335F95F28A664DB4A21289D2AA053B42E7D16D@xxxxxxxxxxxxxxxxxxx>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

>>> On 05.07.10 at 16:23, "Huang2, Wei" <Wei.Huang2@xxxxxxx> wrote:
> 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 

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. 

Jan


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

WARNING - OLD ARCHIVES

xen-devel

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