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: "H. Peter Anvin" <hpa@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH 06/16] xen: disable PAT
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Sun, 10 May 2009 10:21:48 +0100
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Jeremy Fitzhardinge <Jeremy.Fitzhardinge@xxxxxxxxxx>, Suresh Siddha <suresh.b.siddha@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>, "Pallipadi, Venkatesh" <venkatesh.pallipadi@xxxxxxxxx>, "Linux@xxxxxxxxx" <Linux@xxxxxxxxx>, Lu <yinghai@xxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxx>, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>, Arjan van de Ven <arjan@xxxxxxxxxxxxx>
Delivery-date: Sun, 10 May 2009 02:22:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A05CD29.6050505@xxxxxxxxx>
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: AcnQ1RsVsbaPt7aeQIGlps/deltZxwAe6Nkw
Thread-topic: [Xen-devel] Re: [PATCH 06/16] xen: disable PAT
User-agent: Microsoft-Entourage/12.17.0.090302
On 09/05/2009 19:36, "H. Peter Anvin" <hpa@xxxxxxxxx> wrote:

>> My suggestion is that Xen changes its PAT[1] from WT to WC. AFAIK only
>> suse's Linux port is currently using Xen's PAT support, and it does not
>> actually use the WT cache attribute. Then Xen's PAT[0-3] would match what
>> Linux expects, and Linux apparently does not risk using PAT[4-7] because of
>> processor errata so their values are irrelevant. Linux can check that it is
>> running on Xen with suitable PAT setup by reading MSR_IA32_CR_PAT and
>> checking PAT[0-3], and only enable PAT usage in case of a match.
> 
> There exists at least one processor erratum where the CPU will use
> PAT[4-7] when the user requested PAT[0-3].  For those CPUs, it is unsafe
> for *any* OS to have PAT[4-7] != PAT[0-3].

Would it be unreasonable for us to disable PAT on such processors?

An alternative would be to set up PAT according to a new elfnote in the dom0
kernel image, and then only expose the PAT feature flag to domU kernels that
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?).

 -- Keir



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

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