linux-kernel - Re: [PATCH 00/18] 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: <20070316114415.GA26403@one.firstfloor.org>
Date:	Fri, 16 Mar 2007 12:44:15 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Christoph Lameter <clameter@....com>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	Andi Kleen <andi@...stfloor.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Martin Bligh <mbligh@...igh.org>, Ingo Molnar <mingo@...e.hu>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Chris Wright <chrisw@...s-sol.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Glauber de Oliveira Costa <glommer@...il.com>
Subject: Re: [PATCH 00/18] Make common x86 arch area for i386 and x86_64 - Take 2

> In the future it is likely that x86_64 will significantly deviate from 

It already is in some cases. And I agree more will happen.

> i386. i386 is going to be gradually abandoned because it does not support 
> the ever larger memory sizes and be mainly used for embedded devices. 

The desktop/server user base is quite conservative so that will take a long 
time, but gradually probably.

> x86_64 is going to acquire more functionality that will not be available 
> for i386. We plan f.e. to add virtual memmap support for x86_64. Virtual 

What advantage would that have over the current setup?
We already should handle holes between nodes reasonably efficiently
and with nonlinear memory even holes inside nodes shouldn't be a problem.

> memmap support may require a large chunk of virtual memory space that is 
> not available on i386. Its not good to have to deal with i386 issues when 
> doing x86_64 arch development.

If the great merged architecture ever happens this would be needed anyways.
Just basic 32bit support isn't too difficult anyways -- the problem 
are more the old bugs.

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