[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46A14D0C.7090007@zytor.com>
Date: Fri, 20 Jul 2007 17:02:20 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
CC: Jeff Garzik <jeff@...zik.org>,
Thomas Gleixner <tglx@...utronix.de>,
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>,
Arjan van de Ven <arjan@...radead.org>,
Chris Wright <chrisw@...s-sol.org>,
Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [RFC, Announce] Unified x86 architecture, arch/x86
Alan Cox wrote:
> On Fri, 20 Jul 2007 18:38:39 -0400
> Jeff Garzik <jeff@...zik.org> wrote:
>
>> I agree with Andi... it's quite nice to be able to leave some arch/i386
>> stuff, and not carry it over to arch/x86-64.
>
> Its easy enough to push that stuff into arch/x86/legacy and have one
> subdirectory of stuff to pull in for ancient systems.
The other thing is that "legacy" in this context is fungible. No IOMMU
was legacy until the Intel x86-64 chips came out, and I can promise you
that some legacy code will be necessary once we start seeing VIA and
others come out with embedded x86-64.
On the other hand, it's pretty bloody safe to assume that we'll never
see an x86-64 chip without CPUID, CMOV, FXSAVE, SSE-2, CMPXCHG, etc.
-hpa
-
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