WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] [PATCH][SVM] remove FFXSR CPUID bit for AMD-V HVM guests

To: "Jan Beulich" <jbeulich@xxxxxxxxxx>, "Woller, Thomas" <thomas.woller@xxxxxxx>
Subject: RE: [Xen-devel] [PATCH][SVM] remove FFXSR CPUID bit for AMD-V HVM guests
From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
Date: Thu, 1 Feb 2007 12:10:06 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 01 Feb 2007 03:10:02 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <45C1B0CB.76E4.0078.0@xxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcdF2aJwwXant2fxRq+2hWH0V1iNYgAF7ZBg
Thread-topic: [Xen-devel] [PATCH][SVM] remove FFXSR CPUID bit for AMD-V HVM guests
 

> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Jan Beulich
> Sent: 01 February 2007 08:20
> To: Woller, Thomas
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] [PATCH][SVM] remove FFXSR CPUID bit 
> for AMD-V HVM guests
> 
> >>> "Woller, Thomas" <thomas.woller@xxxxxxx> 01.02.07 00:06 >>>
> >Remove visibility of the FFXSR CPUID bit to an HVM guest.
> >This patch allows HVM Windows x64 to install/boot on AMD-V platforms.
> 
> Would you mind explaining why this is necessary? (Similarly I 
> have a hard
> time understanding why 3dnow can't be allowed for hvm guests.)

I don't know why FFXSR shouldn't be allowed... 

3Dnow! should be allowed in the guest, however, MMIO from SSE/3Dnow!/MMX
instructions would fail - but that's no reason to disallow 3DNow!

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



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