linux-kernel - Re: [PATCH] x86: pat cpu feature bit setting for known cpus

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: <47E9948C.3070807@zytor.com>
Date:	Tue, 25 Mar 2008 17:10:52 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Yinghai Lu <yhlu.kernel@...il.com>
CC:	Ingo Molnar <mingo@...e.hu>,
	Venki Pallipadi <venkatesh.pallipadi@...el.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	kernel list <linux-kernel@...r.kernel.org>,
	suresh.b.siddha@...el.com
Subject: Re: [PATCH] x86: pat cpu feature bit setting for known cpus

Yinghai Lu wrote:
> On Tue, Mar 25, 2008 at 4:06 PM, H. Peter Anvin <hpa@...or.com> wrote:
>> Yinghai Lu wrote:
>>  >>
>>  >>  By the way, I want to clarify: I didn't mean it was *intended* as
>>  >>  vendor-lockin, just that it's an undesirable effect of this.
>>  >
>>  > if the PAT works, we may need to trim the memory according to MTRR, right?
>>  >
>>
>>  That doesn't seem like it's specific to PAT?
> 
> could page table to  set WRBACK the range that is not covered by MTRR in e820..
> 

We have to trim anyway... lest we end up using uncached memory and then 
we're in a world of hurt.

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