From: Michal Marek <mmarek@suse.cz>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Jaswinder Singh Rajput <jaswinderlinux@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: config automatically switches from 32-bit to 64-bit for x86
Date: Thu, 3 Jun 2010 15:30:55 +0200 [thread overview]
Message-ID: <20100603133055.GA27797@sepie.suse.cz> (raw)
In-Reply-To: <20100527184653.GA11830@merkur.ravnborg.org>
On Thu, May 27, 2010 at 08:46:53PM +0200, Sam Ravnborg wrote:
> On Thu, May 27, 2010 at 11:49:16AM -0400, Christoph Hellwig wrote:
> > On Thu, May 27, 2010 at 05:37:36AM +0530, Jaswinder Singh Rajput wrote:
> > > Hello,
> > >
> > > I am trying to build 32 bit kernel image on 64-bit machine but after
> > > 'make menuconfig' it automatically switches 32-bit to 64-bit.
> > >
> > > Is this a BUG or did intentionally.
> >
> > I think it's intentional, but I'm really annoyed by this behaviour.
>
> The request when we did the merge of 32 and 64 bit was that we
> should continue to build 64bit kernels on 64 bit machines.
> And likewise for 32bit.
> Because this was what the users where used to.
>
> We could simplify metters by defining new rules.
> As you suggest that uname on an intel box always resulted in ARCH=x86.
> But then people would complain why a 32 bit kernel is default when
> the box is 64 bit.
Which is not acceptable, IMO. An x86_64 distro typically has a complete
64bit userspace including /sbin/init, so the default kernel has to be
64bit.
What about always making the prompt visible, so that the previously set
value gets reused? The downside is that 'make ARCH=i386 menuconfig' in a
clean tree on x86_64 will default to 64bit, because it will find the
setting in the config of the running 64bit kernel :(. But after manually
turning CONFIG_64BIT off, the setting will be preserved.
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index dcb0593..05ec418 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -3,7 +3,7 @@ mainmenu "Linux Kernel Configuration for x86"
# Select 32 or 64 bit
config 64BIT
- bool "64-bit kernel" if ARCH = "x86"
+ bool "64-bit kernel"
default ARCH = "x86_64"
---help---
Say yes to build a 64-bit kernel - formerly known as x86_64
next prev parent reply other threads:[~2010-06-03 13:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 0:07 Jaswinder Singh Rajput
2010-05-27 0:13 ` Rafael J. Wysocki
2010-05-27 4:09 ` Jaswinder Singh Rajput
2010-05-27 4:31 ` Américo Wang
2010-05-27 5:23 ` Jaswinder Singh Rajput
2010-05-27 9:03 ` Américo Wang
2010-05-27 5:31 ` Randy Dunlap
2010-05-27 16:19 ` Geert Uytterhoeven
2010-05-27 20:21 ` Rafael J. Wysocki
2010-05-27 15:19 ` Matthias Schniedermeyer
2010-05-27 15:49 ` Christoph Hellwig
2010-05-27 16:11 ` Matthias Schniedermeyer
2010-05-27 16:13 ` Christoph Hellwig
2010-05-27 16:35 ` Matthias Schniedermeyer
2010-05-27 18:46 ` Sam Ravnborg
2010-05-27 22:07 ` Jaswinder Singh Rajput
2010-05-29 11:19 ` Sam Ravnborg
2010-05-29 17:19 ` Jaswinder Singh Rajput
2010-06-02 8:20 ` Américo Wang
2010-06-02 8:50 ` Sam Ravnborg
2010-06-03 13:30 ` Michal Marek [this message]
2010-06-04 6:23 ` Jaswinder Singh Rajput
2010-06-04 7:53 ` Michal Marek
2010-06-06 4:14 ` Jaswinder Singh Rajput
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=20100603133055.GA27797@sepie.suse.cz \
--to=mmarek@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=jaswinderlinux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=x86@kernel.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®