From: Adrian Bunk <bunk@kernel.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>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/11 v3] enable "make ARCH=x86"
Date: Sat, 10 Nov 2007 11:13:24 +0100 [thread overview]
Message-ID: <20071110101324.GK26163@stusta.de> (raw)
In-Reply-To: <47356A84.9020106@garzik.org>
On Sat, Nov 10, 2007 at 03:23:32AM -0500, Jeff Garzik wrote:
> Sam Ravnborg wrote:
>> Keeping ARCH=i386 and ARCH=x86_64 around is just a way to pretend
>> this is two diffrent architectures which is no longer the case.
>
> They _are_ different in the real world... that's why
>
> make ARCH=i386
>
> is so often used.
I for one use i386 simply because I do not have any computer that would
support 64bit. But when I'll see a 32/64bit question during
"make oldconfig" I'll also know what to answer.
>> Do we need a way to say "build a kernel that is 64 bit"?
>> If we need this then we should look at the most intuitive way
>> to say so and this should work across x86, powerpc and s390.
>>
>> make 64BIT=y ARCH=x86
>>
>> looks so much more intuitive. And it is generic.
>> This is just a proposal.
>
> Or the short and straightforward
>
> make ARCH=x86_64
>
> to do the same thing (and incidentally what we've been doing up until this
> point).
>
> Don't get so hung up on "architecture" and actually look at what people do
> _today_.
>
> All other solutions proposed are simply _longer_ ways to do exact the same
> thing. "more work for same outcome" isn't optimal.
Let's check who the "people" affected are:
Aunt Tillie isn't affected since she doesn't compile her own kernel.
People compiling kernels have to learn that the choice went from
ARCH={i386,x86_64} to a Kconfig option. I'd say it's more consistent
that the 32/64bit question is now handled the same way as the
K6/K7/K8/... question. And there doesn't seem to be any "longer" or
"more work" in this case.
What's left are kernel developers who have not read the toplevel README
and who do therefore not know about KCONFIG_ALLCONFIG. Getting people to
write documentation is a hard task, but it's only second to getting
people to read documentation....
And although you might argue that you have a few characters more to type
when using KCONFIG_ALLCONFIG it has the advantage that it's generic,
and it e.g. allows you to create a CONFIG_X86_32=y, CONFIG_SMP=n
allyesconfig configuration.
> Jeff
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-11-10 10:13 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 23:08 [PATCH 0/11 v3] enable "make ARCH=x86" Sam Ravnborg
2007-11-09 23:20 ` [PATCH 01/11] x86: unification of cfufreq/Kconfig Sam Ravnborg
2007-11-09 23:20 ` [PATCH 02/11] x86: start unification of arch/x86/Kconfig.* Sam Ravnborg
2007-11-09 23:20 ` [PATCH 03/11] x86: arch/x86/Kconfig.cpu unification Sam Ravnborg
2007-11-09 23:20 ` [PATCH 04/11] x86: add X86_32 dependency to i386 specific symbols in Kconfig.i386 Sam Ravnborg
2007-11-09 23:20 ` [PATCH 05/11] x86: add X86_64 dependency to x86_64 specific symbols in Kconfig.x86_64 Sam Ravnborg
2007-11-09 23:20 ` [PATCH 06/11] x86: copy x86_64 specific Kconfig symbols to Kconfig.i386 Sam Ravnborg
2007-11-09 23:20 ` [PATCH 07/11] x86: move all simple arch settings to Kconfig Sam Ravnborg
2007-11-09 23:20 ` [PATCH 08/11] x86: move the rest of the menu's " Sam Ravnborg
2007-11-09 23:20 ` [PATCH 09/11] x86: enable "make ARCH=x86" Sam Ravnborg
2007-11-09 23:20 ` [PATCH 10/11] x86: drop backward compatibility symlinks to i386/boot and x86_64/boot Sam Ravnborg
2007-11-09 23:20 ` [PATCH 11/11] kbuild: sanity check the specified arch Sam Ravnborg
2007-11-10 3:23 ` [PATCH 0/11 v3] enable "make ARCH=x86" Jeff Garzik
2007-11-10 3:37 ` Randy Dunlap
2007-11-10 3:50 ` Adrian Bunk
2007-11-10 4:05 ` Brian Gerst
2007-11-10 4:12 ` Jeff Garzik
2007-11-14 20:13 ` Roman Zippel
2007-11-10 7:54 ` Sam Ravnborg
2007-11-10 5:26 ` Nick Piggin
2007-11-10 8:21 ` Paul Mundt
2007-11-10 8:24 ` Jeff Garzik
2007-11-10 8:44 ` Paul Mundt
2007-11-10 20:35 ` H. Peter Anvin
2007-11-10 20:46 ` Sam Ravnborg
2007-11-10 21:24 ` Theodore Tso
2007-11-10 9:39 ` Sam Ravnborg
2007-11-10 10:32 ` david
2007-11-10 9:21 ` Adrian Bunk
2007-11-10 9:26 ` Paul Mundt
2007-11-10 8:23 ` Jeff Garzik
2007-11-10 10:13 ` Adrian Bunk [this message]
2007-11-10 15:53 ` Christoph Hellwig
2007-11-12 11:59 ` Frans Pop
[not found] <9nL9f-2n8-11@gated-at.bofh.it>
[not found] ` <9nPcU-bm-3@gated-at.bofh.it>
[not found] ` <9nTqh-6Cw-7@gated-at.bofh.it>
[not found] ` <9nTTh-7w5-7@gated-at.bofh.it>
[not found] ` <9nTTh-7w5-5@gated-at.bofh.it>
[not found] ` <9nUcv-7UA-7@gated-at.bofh.it>
[not found] ` <9o5hA-b8-7@gated-at.bofh.it>
[not found] ` <9o640-1rJ-1@gated-at.bofh.it>
2007-11-11 21:03 ` Bodo Eggert
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=20071110101324.GK26163@stusta.de \
--to=bunk@kernel.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 \
--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