From: Andi Kleen <andi@firstfloor.org>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
mingo@elte.hu, Alan <alan@lxorguk.ukuu.org.uk>,
Gerd Hoffmann <kraxel@redhat.com>,
jeremy@goop.org, Andi Kleen <andi@firstfloor.org>,
"H. Peter Anvin" <hpa@zytor.com>,
JBeulich@novell.com, jbarnes@virtuousgeek.org
Subject: Re: [Xen-devel] Re: [GIT PULL] xen /proc/mtrr implementation
Date: Mon, 25 May 2009 11:15:30 +0200 [thread overview]
Message-ID: <20090525091530.GW846@one.firstfloor.org> (raw)
In-Reply-To: <4A1A59DD.7030101@wpkg.org>
> Are these ones (below) good CPU to worry about? That's slightly
> off-topic as they are KVM guests, but still, the guest kernel seems to
> disable PAT (unless I'm mistaken).
To my knowledge the only CPUs with broken PAT are some very old Pentium
Pros dating from back the time when PAT was new and noone used it.
On those it should be disabled or the high bits not used.
The kernel is overall too conservative with its white list.
Today a lot of other common operating systems use PAT extensively,
so in general it works on the hardware level.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-05-25 9:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 8:42 [Xen-devel] Re: [GIT PULL] xen /proc/mtrr implementation Tomasz Chmielewski
2009-05-25 9:15 ` Andi Kleen [this message]
2009-05-25 9:31 ` Jan Beulich
2009-05-25 9:47 ` Andi Kleen
2009-05-25 16:05 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2009-05-12 23:27 Jeremy Fitzhardinge
2009-05-13 13:30 ` Ingo Molnar
2009-05-13 14:39 ` Jeremy Fitzhardinge
2009-05-15 18:27 ` Ingo Molnar
2009-05-15 20:09 ` Jeremy Fitzhardinge
2009-05-15 23:26 ` Eric W. Biederman
2009-05-15 23:49 ` Jeremy Fitzhardinge
2009-05-16 3:22 ` Jesse Barnes
2009-05-16 4:26 ` Eric W. Biederman
2009-05-18 4:57 ` Jeremy Fitzhardinge
2009-05-18 8:59 ` Ingo Molnar
2009-05-18 13:17 ` [Xen-devel] " Jan Beulich
2009-05-18 18:07 ` Jeremy Fitzhardinge
2009-05-19 9:59 ` Ingo Molnar
2009-05-19 10:22 ` [Xen-devel] " Jan Beulich
2009-05-19 11:08 ` Ingo Molnar
2009-05-19 12:04 ` Gerd Hoffmann
2009-05-19 12:26 ` Ingo Molnar
2009-05-19 12:32 ` Alan Cox
2009-05-19 12:37 ` Ingo Molnar
2009-05-19 13:21 ` Gerd Hoffmann
2009-05-19 13:31 ` Ingo Molnar
2009-05-19 13:51 ` Gerd Hoffmann
2009-05-19 14:17 ` Ingo Molnar
2009-05-19 14:55 ` Gerd Hoffmann
2009-05-19 15:24 ` Ingo Molnar
2009-05-20 8:01 ` Gerd Hoffmann
2009-05-20 16:35 ` Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090525091530.GW846@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=JBeulich@novell.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=jeremy@goop.org \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mangoo@wpkg.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.