linux-kernel - Re: [PATCH take3 00/20] Make common x86 arch area for i386 and x86_64

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: <20070316102933.GB4185@elte.hu>
Date:	Fri, 16 Mar 2007 11:29:33 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Chris Wright <chrisw@...s-sol.org>,
	Rusty Russell <rusty@...tcorp.com.au>, Andi Kleen <ak@....de>,
	Glauber de Oliveira Costa <glommer@...il.com>,
	Jeremy Fitzhardinge <jeremy@...p.org>
Subject: Re: [PATCH take3 00/20] Make common x86 arch area for i386 and x86_64 - Take 3

* Steven Rostedt <rostedt@...dmis.org> wrote:

> Once again here's an attempt to put the shared files of x86_64 and 
> i386 into a separate directory.

what do you think about the idea i suggested: to do an x32_/x64_ prefix 
(or _32/_64 postfix), in a brute-force way, _right away_. I.e. do not 
have any overlap of having both arch/i386/ and arch/x86_64/ and 
arch/x86/ - move everything to arch/x86/ right now.

in the initial step we dont even have to attempt to share anything - we 
just want to make sure everything still works fine. Just create a 
'unified' layout with the prefix/postfix solution, and make sure that 
the build architecture can compile existing .configs just fine, which 
results in a functionally identical vmlinux that would be built if these 
files were still in arch/i386/ (and arch/x86_64/).

i dont think we want to have a too long 'overlap' period. Lets just 
unify them, that would be the only large-scale intrusive move.

>From that point on, the unification decisions would be largely per-file: 
"do we want to unify process_32.c and process_64.c into the same file?".

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