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: <30701c46-a57e-49f2-9273-6f725c8463e0@email.android.com>
Date:	Sat, 29 Sep 2012 08:05:15 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Henrique de Moraes Holschuh <hmh@....eng.br>
CC:	Peter Hurley <peter@...leysoftware.com>,
	"zhenzhong.duan@...cle.com" <zhenzhong.duan@...cle.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"x86@...nel.org" <x86@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] x86: mtrr: Constrain WB MTRR to max phys mem prior to cleanup

PAT support are lacking only in the Pentium Pro and Pentium II.  Sorry, if you're using crap that old, you don't get to screw up the kernel for everyone else.

Henrique de Moraes Holschuh <hmh@....eng.br> wrote:

>On Fri, 28 Sep 2012, H. Peter Anvin wrote:
>> On 09/28/2012 10:37 AM, Peter Hurley wrote:
>> > An interesting side note: more recent revisions of this BIOS (rev.
>A11)
>> > report one less variable MTRR (so, IA32_MTRRCAP is writable?)
>> > 
>> >>> However, the right way to fix that is to use the PAT interfaces,
>which 
>> >>> doesn't have this drawback -- then MTRR cleanup becomes entirely 
>> >>> superfluous and the problem goes away.
>> >> Do you mean disable MTRR totally here?
>> > 
>> > Well, since PAT entries marked WC override all MTRR settings,
>whatever
>> > the BIOS set the variable MTRRs to becomes irrelevant, so not
>disabled
>> > but rather ignored.
>> > 
>> 
>> The whole point is that the display stuff should not use MTRR, but
>> rather use PAT to provide WC.  Then we don't need to "clean up" the
>> BIOS-set MTRRs.
>
>What about my trusty ThinkPad T43, and other ia32 boxes that either
>lack PAT
>support, or have it blacklisted?
>
>These are exactly the boxes that will _never_ get a BIOS fix if their
>MTRRs
>are screwed up...

-- 
Sent from my mobile phone. Please excuse brevity and lack of formatting.
--
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