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] Re: [PATCH 06/16] xen: disable PAT

To: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH 06/16] xen: disable PAT
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Sun, 10 May 2009 18:34:11 +0100
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Jeremy Fitzhardinge <Jeremy.Fitzhardinge@xxxxxxxxxx>, Suresh Siddha <suresh.b.siddha@xxxxxxxxx>, "Pallipadi, Venkatesh" <venkatesh.pallipadi@xxxxxxxxx>, the arch/x86 maintainers <x86@xxxxxxxxxx>, Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, "Linux@xxxxxxxxx" <Linux@xxxxxxxxx>, Lu <yinghai@xxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxx>, Arjan van de Ven <arjan@xxxxxxxxxxxxx>
Delivery-date: Sun, 10 May 2009 10:34:52 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090510142928.66bb57bb@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcnRc0G7JonX0J8QSYWYAHtcYY5xigAIkW/w
Thread-topic: [Xen-devel] Re: [PATCH 06/16] xen: disable PAT
User-agent: Microsoft-Entourage/12.17.0.090302
On 10/05/2009 14:29, "Alan Cox" <alan@xxxxxxxxxxxxxxxxxxx> wrote:

>> have matching PAT configuration. No elfnote would mean use Xen's existing
>> PAT setup (or if that's very dangerous then disable PAT altogether, perhaps
>> dependent on CPU model/stepping?).
> 
> Hiding it on errata hit processors if the guest cannot support PAT
> safely on such processors sounds a good policy and its one being a
> hypervisor you can do neatly.
> 
> There are quite a few different CPUs with PAT errata. I've no idea why
> there are so many errata about that specific bit.

Okay, this sounds like a good way to then. I can work out details with
Jeremy from here, and this will then have no impact on Linux PAT logic. If
we advertise PAT to Linux via CPUID, that will mean PAT is set up just as
Linux requires.

 Thanks,
 Keir



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

<Prev in Thread] Current Thread [Next in Thread>