[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Re: [PATCH]: blacklist new AMD CPUID bits for PV domains


  • To: Andre Przywara <andre.przywara@xxxxxxx>
  • From: Keir Fraser <keir@xxxxxxx>
  • Date: Tue, 25 Jan 2011 14:56:28 +0000
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 25 Jan 2011 06:57:47 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=hReMbzDfC7IQF2fMzGCwfoJ6g9jCJAoed21OnJiJPmPSJtmdpxcAvRzMM8NojCdAbh X18N/0+Fbvlza7qsgu1srKQ6qkwOB9Fa3hmYm78R4hAeaoATZgxmDQjYSD4DIfAafEty lZ+C8XuUi9Yi3nbq3HKQbV/EBAO3LtL1SD3r0=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acu8oAtEURNAD/IZ2EqvC4QadNskqg==
  • Thread-topic: [PATCH]: blacklist new AMD CPUID bits for PV domains

On 25/01/2011 14:14, "Andre Przywara" <andre.przywara@xxxxxxx> wrote:

> Hi,
> 
> there are some new CPUID bits (and leaves) which Dom0 and PV domains
> should not see to avoid trouble, since we don't emulate the features.
> The most prominent one is a topology leaf, which contains information
> specific to the physical CPU, not the virtual one. To avoid confusion
> (and possibly crashes) due to a confused Dom0 scheduler simply disable
> these bits.
> 
> Signed-off-by: Andre Przywara <andre.przywara@xxxxxxx>

Andre,

You also need to mask these in tools/libxc/xc_cpuid_x86.c, right? The
hypervisor code you modify affects only dom0.

 -- Keir




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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.