From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Chris Wright <chrisw@sous-sol.org>,
Rusty Russell <rusty@rustcorp.com.au>, Andi Kleen <ak@muc.de>,
Glauber de Oliveira Costa <glommer@gmail.com>
Subject: Re: [RFC/PATCH 00/59] Make common x86 arch area for i386 and x86_64
Date: Tue, 13 Mar 2007 21:02:15 -0400 [thread overview]
Message-ID: <1173834135.30118.14.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0703131432400.9690@woody.linux-foundation.org>
On Tue, 2007-03-13 at 14:39 -0700, Linus Torvalds wrote:
>
> 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.
That's actually a larger goal, but for the immediate future, I figure
this would be a good first step. Start out by stating what's similar,
and then build off of this for something bigger. But in the mean time,
we can have a staging ground for work that's for both i386 and x86_64
archs. And for those that know these systems in a more intimate way
(Andi :) they can work off of this to make that monster.
-- Steve
next prev parent reply other threads:[~2007-03-14 1:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1173820919.28042.3.camel@localhost.localdomain>
2007-03-13 21:39 ` Linus Torvalds
2007-03-14 1:02 ` Steven Rostedt [this message]
2007-03-14 10:12 ` Andi Kleen
2007-03-14 22:05 ` Rusty Russell
2007-03-14 12:49 ` Ingo Molnar
2007-03-13 21:45 ` Chris Wright
2007-03-14 1:05 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1173834135.30118.14.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=ak@muc.de \
--cc=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.org \
--cc=glommer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®