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

Message-ID: <48BAB074.50809@zytor.com>
Date:	Sun, 31 Aug 2008 07:53:40 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Krzysztof Helt <krzysztof.h1@...pl>
CC:	linux-kernel@...r.kernel.org, tglx@...utronix.de, mingo@...hat.com
Subject: Re: [PATCH] x86: amd k6-2 mtrr not detected fix

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.)

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