linux-kernel - Re: [PATCH] x86: amd k6-2 mtrr not detected fix

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] [day] [month] [year] [list]

Message-ID: <86802c440808312045x508ac0fbu3c9408b26f823ce7@mail.gmail.com>
Date:	Sun, 31 Aug 2008 20:45:33 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	"Krzysztof Helt" <krzysztof.h1@...pl>,
	linux-kernel@...r.kernel.org, tglx@...utronix.de, mingo@...hat.com
Subject: Re: [PATCH] x86: amd k6-2 mtrr not detected fix

On Sun, Aug 31, 2008 at 7:53 AM, H. Peter Anvin <hpa@...or.com> wrote:
> Krzysztof Helt wrote:
>>
>> It seems that the same problem affects Cyrix and
>> Centaur/VIA cpus. Can some x86 guy inspect the
>> mtrr initialization code ?
>>
>
> *GROAN*
>
> I would prefer if we could move the CPU detection code before the MTRR code;
> I don't think there is an inherent reason why we shouldn't be able to.  It
> would be much preferrable to scattering all kinds of CPU detection
> information all over the system.
>
> I am going to be away today so I can't look at this myself until tomorrow at
> the earliest (tomorrow is a holiday here, though, so I can't promise I'll be
> around then either.)
>
will send one for Helt to test it...

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