linux-kernel - Re: 2.6.26-rc6-git2: Reported regressions from 2.6.25

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: <alpine.LFD.1.10.0806141654280.2949@woody.linux-foundation.org>
Date:	Sat, 14 Jun 2008 17:00:48 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	"Maciej W. Rozycki" <macro@...ux-mips.org>
cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Adrian Bunk <bunk@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Natalie Protasevich <protasnb@...il.com>,
	"David S. Miller" <davem@...emloft.net>
Subject: Re: 2.6.26-rc6-git2: Reported regressions from 2.6.25



On Sat, 14 Jun 2008, Maciej W. Rozycki wrote:
> 
>  From what you have written it looks the dependency should actually be:
> 
> 	depends on !M386 && !M486 && !M586 && !M586TSC && !M586MMX
> 
> as none of the pre-Pentium-Pro processors had the PAE feature (I am not
> sure about non-Intel implementations, so the case of M586 would have to be
> investigated).

Yes, it's the non-intel ones that would keep me from saying !M586.

For intel, PAE was a PPro feature (at least officially, as you point out), 
but I do not know about various other manufacturers. From personal 
experience, the line between Pentium and PPro features doesn't tend to be 
totally black-and-white (although I suspect that when it comes to PAE it 
_may_ be).

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