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: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH 06/16] xen: disable PAT
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Mon, 11 May 2009 10:09:22 +0100
Cc: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 11 May 2009 02:08:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C62CCEA3.AB56%keir.fraser@xxxxxxxxxxxxx>
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>
References: <20090510142928.66bb57bb@xxxxxxxxxxxxxxxxxxx> <C62CCEA3.AB56%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> Keir Fraser <keir.fraser@xxxxxxxxxxxxx> 10.05.09 19:34 >>>
>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.

Depending on what exact plans you have here, I would question whether
having an upper layer dictate mechanisms used by a lower layer. In
particular, just like with the same mistake made with kexec,
- Linux's use of PAT may change (specifically, the value it writes to the PAT
  MSR may not be statically determinable at some point, making the ELF note
  approach you indicated as a possible solution unusable)
- the interface may not be suitable for non-Linux
Hence I'd appreciate if working out the details here could be done in public.

Thanks, Jan


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

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