lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <C62CCEA3.AB56%keir.fraser@eu.citrix.com>
Date:	Sun, 10 May 2009 18:34:11 +0100
From:	Keir Fraser <keir.fraser@...citrix.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	"H. Peter Anvin" <hpa@...or.com>,
	Ian Campbell <Ian.Campbell@...citrix.com>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	the arch/x86 maintainers <x86@...nel.org>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	"Linux@...or.com" <Linux@...or.com>,
	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>,
	Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Jeremy Fitzhardinge <Jeremy.Fitzhardinge@...rix.com>,
	Xen-devel <xen-devel@...ts.xensource.com>,
	Jan Beulich <jbeulich@...ell.com>, Ingo Molnar <mingo@...e.hu>,
	Lu <yinghai@...nel.org>, Thomas Gleixner <tglx@...utronix.de>,
	Arjan van de Ven <arjan@...radead.org>
Subject: Re: [Xen-devel] Re: [PATCH 06/16] xen: disable PAT

On 10/05/2009 14:29, "Alan Cox" <alan@...rguk.ukuu.org.uk> 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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ