linux-kernel - Re: [RFC/PATCH 00/59] Make common x86 arch area for i386 and x86

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

Date:	Tue, 13 Mar 2007 14:39:33 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Steven Rostedt <rostedt@...dmis.org>
cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Chris Wright <chrisw@...s-sol.org>,
	Rusty Russell <rusty@...tcorp.com.au>, Andi Kleen <ak@....de>,
	Glauber de Oliveira Costa <glommer@...il.com>
Subject: Re: [RFC/PATCH 00/59] Make common x86 arch area for i386 and x86_64

On Tue, 13 Mar 2007, Steven Rostedt wrote:
> 
> What we have currently is a bunch of hacks.  Seems that people can't make
> up their mind to what to do.

I don't mind the patches, but I'd be a lot happier if it also was a stated 
intention to actually make it be buildable as "x86", the same way that the 
separate 32-bit and 64-bit POWER architectures were merged into just one 
architecture that could be built either way.

For the POWER merge, we had (and probably still have) legacy platforms 
that could only be built the old way (ie if you needed to build for 
certain legacy 32-bit targets, you still needed to use the "ppc" 
architecture, so I'm not saying that it has to all be converted, but I 
think that we should at least *aim* for unifying 32-bit and 64-bit x86.

The "32-bit code has legcay issues" thing that Andi complained about (eg 
there's no guarantee of a HPET on 32-bit x86) doesn't really change the 
fact that yes, we have to support those legacy issues *anyway*, and 64-bit 
x86 certainly has its set of issues already too.

We've started to notice that the i386 build gets broken now that most 
developers tend to have newer CPU's and run mostly on x86-64 (and yes, 
that's me too), and while I don't think unifying things will guarantee 
that doesn't happen in the future, it will hopefully at least help make it 
not get much *worse*.

As it is, the build environment has to know to pass in "-m32/-m64" 
anyway..

		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/