linux-kernel - Re: [PATCH 0/2] PAT support for i386 and x86

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]

Date:	Tue, 7 Aug 2007 10:30:04 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Cédric Augonnet <cedric.augonnet@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>,
	Andi Kleen <andi@...stfloor.org>, loic@...i.com,
	brice@...i.com, cedric.augonnet@...-lyon.org
Subject: Re: [PATCH 0/2] PAT support for i386 and x86_64

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

-
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/