linux-kernel - Re: Re: [PATCH] x86: set Pentium M as PAE capable

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]

Date:	Sun, 2 Mar 2014 21:56:19 +0100
From:	Andreas Mohr <andi@...as.de>
To:	Chris Bainbridge <chris.bainbridge@...il.com>
Cc:	Dennis Mungai <dmngaie@...il.com>, Borislav Petkov <bp@...en8.de>,
	"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
	Dave Jones <davej@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: Re: [PATCH] x86: set Pentium M as PAE capable

Hi,

>  	/*
> +	 * PAE CPUID bug: Pentium M reports no PAE but has PAE
> +	 */

Ain't that a tad strongly/incorrectly worded?

It's probably not certain whether that's a "bug".
Prior content in this discussion suggested that the flag might have been
intentionally not advertised, due to not being of sufficient quality
yet in these revisions.
Also, it's not definite that it has "PAE" in a usable form.

So what about rewording it into an "issue", e.g. something like:

"PAE CPUID issue: most Pentium M report no PAE but may have PAE
implemented at a potentially usable quality level.

Thank you very much for this important deescalation work of the quite annoying
PAE compat issue! (Pentium M, AMD Geode, VIA C7, <(=?) Pentium II, ...)

(BTW, would it be possible to transform Linux's PAE support into
boot-config or even fully runtime-detectable boot switching to
(non-)PAE, similar to or exceeding what XP offers with its static
boot-time flag?
Last time I checked PAE support config defines were spread over ~ 40
kernel source files though :-((()

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