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: <1184972499.2692.9.camel@laptopd505.fenrus.org>
Date:	Fri, 20 Jul 2007 16:01:39 -0700
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...l.org>,
	Andrew Morton <akpm@...l.org>, Andi Kleen <ak@...e.de>,
	Ingo Molnar <mingo@...e.hu>,
	Chris Wright <chrisw@...s-sol.org>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [RFC, Announce] Unified x86 architecture, arch/x86

On Sat, 2007-07-21 at 00:32 +0200, Thomas Gleixner wrote:
> We are pleased to announce a project we've been working on for some 
> time: the unified x86 architecture tree, or "arch/x86" - and we'd like 
> to solicit feedback about it.



I really like the idea of a unified source tree for the 2 x86 variants.
The technical differences are really small (of course there are
differences, especially in the boot sequence), and striving to unify as
much as possible while having a clean way to do per 32/64 bit parts as
well is something that imo is the right thing.

I'm more than happy to help with this effort, and have people in my
group at Intel help test and engineer this as well.

The technical approach of first moving (in an automated way) everything
into one directory, and then merge pieces one by one is appealing since
it can be done incrementally and carefully, while testing the "can we do
separate bits" from the start.

So in short, way to go, I hope we can get this thing done as soon as
possible. Heck it looks like the infrastructure (not the unification)
can make it into 2.6.23 merge window still, so that the entire 2.6.23
window can be used to develop merged-functionality pieces...

Greetings,
    Arjan van de Ven


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ