linux-kernel - Re: [BUG] x86 kenel won't boot under Virtual PC

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:	Mon, 8 Sep 2008 11:42:05 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	linux@...dersweb.net, linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	the arch/x86 maintainers <x86@...nel.org>,
	Andi Kleen <andi-suse@...stfloor.org>
Subject: Re: [BUG] x86 kenel won't boot under Virtual PC

> Under that logic we shouldn't even have CPU configurables, since you 

Just for optimization.

> want it to "just work" whatever crap you're running on.  That is EXACTLY 
> what CONFIG_X86_GENERIC means, and the fact that any particular 

At least when I introduced X86_GENERIC it was just an optimization,
not a requirement.

That is the kernel pretty much always did "just work"
(with only a very few exceptions like PAE vs non PAE) on all 
CPUs. The CPU configs also just specified optimizations, not correctness.
The code for all CPUs used to be always there.
X86_GENERIC was mostly just to do things like always use 
the largest cache alignment.

I think someone changed that recently, but imho that wasn't
an improvement. As you can see it just causes endless support
problems.

> distribution is broken with respect to not enabling it is a bug in that 
> distribution, and not grounds for breaking the upstream kernel.

Well it's more like that you guys changed the semantics 
without warnings the distributions. I'm not sure you can blame
Debian for that.

-Andi
-- 
ak@...ux.intel.com
--
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/