From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir@xen.org>
Subject: Re: [PATCH]: blacklist new AMD CPUID bits for PV domains
Date: Tue, 25 Jan 2011 14:56:28 +0000
Message-ID: <C964951C.12672%keir@xen.org>
References: <4D3EDABD.50202@amd.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <4D3EDABD.50202@amd.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Andre Przywara <andre.przywara@amd.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On 25/01/2011 14:14, "Andre Przywara" <andre.przywara@amd.com> 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@amd.com>

Andre,

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

 -- Keir