From: Andi Kleen <andi@firstfloor.org>
To: "Cédric Augonnet" <cedric.augonnet@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Andi Kleen <andi@firstfloor.org>,
loic@myri.com, brice@myri.com, cedric.augonnet@ens-lyon.org
Subject: Re: [PATCH 0/2] PAT support for i386 and x86_64
Date: Tue, 7 Aug 2007 10:30:04 +0200 [thread overview]
Message-ID: <20070807083004.GB30085@one.firstfloor.org> (raw)
In-Reply-To: <f56c1ba00708061903r29baea3dj6b57032be5820983@mail.gmail.com>
On Mon, Aug 06, 2007 at 10:03:15PM -0400, Cédric Augonnet wrote:
> Hi all,
>
> For quite a while now, there as been numerous attempt to introduce support for
> Page Attribute Table (PAT) in the Linux kernel, whereas most other OS already
> have some support for this feature. Such a proposition popping up periodically,
> perhaps it would be an opportunity to fix that lack for once.
The trouble is you need to avoid conflicting attributes, otherwise
you risk cache corruption. This means the direct mapping needs to be fixed
up and the kernel needs to keep track of the ranges to prevent conflicts.
Also when there is already a MTRR it might not work due to the complicated
rules of MTRR<->PAT interaction.
Then there are old CPU errata that need to be handled etc.
There are also some other issues.
You didn't solve all that at all. If it was as simple as your patch
we would have long done it already.
-Andi
next prev parent reply other threads:[~2007-08-07 8:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 2:03 [PATCH 0/2] PAT support for i386 and x86_64 Cédric Augonnet
2007-08-07 8:30 ` Andi Kleen [this message]
2007-08-08 8:26 ` Loic Prylli
2007-08-08 10:14 ` Andi Kleen
2007-08-08 15:52 ` Cédric Augonnet
[not found] ` <f56c1ba00708080842i1eaa00kef5071d9a1f01f04@mail.gmail.com>
2007-08-08 16:00 ` Andi Kleen
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=20070807083004.GB30085@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@osdl.org \
--cc=brice@myri.com \
--cc=cedric.augonnet@ens-lyon.org \
--cc=cedric.augonnet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=loic@myri.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox