From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] replace "make ARCH=i386/x86_64 with make ARCH=x86"
Date: Sat, 03 Nov 2007 23:20:36 -0700 [thread overview]
Message-ID: <472D64B4.3000306@goop.org> (raw)
In-Reply-To: <472D282B.2000208@garzik.org>
Jeff Garzik wrote:
> This also opens a chicken-and-egg problem... What kind of config is
> generated by allmodconfig when ARCH==x86? There is no good answer.
With a unified x86 architecture, the decision to compile with 32 or
64-bit mode isn't really different from SMP vs UP, PAE vs non-PAE and so
on. It's just a config option with global effects. Over time, the
number of config options with are really 32 or 64-bit specific will
probably pretty small.
> The existing tradition of switching between 32-bit and 64-bit was
> quite nice, and it was done in The Obvious Way(tm) -- via the method
> for specifying the architecture/platform. Switching to Kconfig for
> that decision is a step backwards in usability and IMO violates the
> Principle of Least Surprise.
The architecture is now x86, with a further 32 or 64-bit parameter. We
already have config options for setting the sub-architecture.
J
next prev parent reply other threads:[~2007-11-04 6:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 23:48 [PATCH] replace "make ARCH=i386/x86_64 with make ARCH=x86" Sam Ravnborg
2007-11-03 23:52 ` Arjan van de Ven
2007-11-04 1:17 ` Adrian Bunk
2007-11-04 2:02 ` Jeff Garzik
2007-11-04 2:48 ` Adrian Bunk
2007-11-04 6:20 ` Jeremy Fitzhardinge [this message]
2007-11-05 10:41 ` Christoph Hellwig
2007-11-05 17:17 ` Sam Ravnborg
2007-11-05 21:36 ` Roland Dreier
2007-11-05 21:49 ` Sam Ravnborg
2007-11-05 23:46 ` H. Peter Anvin
2007-11-06 0:40 ` Guillaume Chazarain
2007-11-06 0:47 ` H. Peter Anvin
2007-11-06 1:29 ` Adrian Bunk
2007-11-06 1:33 ` H. Peter Anvin
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=472D64B4.3000306@goop.org \
--to=jeremy@goop.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
/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