From: Borislav Petkov <bp@alien8.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: mingo@kernel.org, hpa@zytor.com, linux-kernel@vger.kernel.org,
tglx@linutronix.de, hpa@linux.intel.com,
David.Woodhouse@intel.com, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/build] x86: Default to ARCH= x86 to avoid overriding CONFIG_64BIT
Date: Sat, 12 Jan 2013 18:06:47 +0100 [thread overview]
Message-ID: <20130112170647.GA10659@liondog.tnic> (raw)
In-Reply-To: <tip-ffee0de411fd4f74f3b788892eeb075abbf26c52@git.kernel.org>
On Thu, Dec 20, 2012 at 06:07:46PM -0800, tip-bot for David Woodhouse wrote:
> Commit-ID: ffee0de411fd4f74f3b788892eeb075abbf26c52
> Gitweb: http://git.kernel.org/tip/ffee0de411fd4f74f3b788892eeb075abbf26c52
> Author: David Woodhouse <dwmw2@infradead.org>
> AuthorDate: Thu, 20 Dec 2012 21:51:55 +0000
> Committer: H. Peter Anvin <hpa@linux.intel.com>
> CommitDate: Thu, 20 Dec 2012 14:37:18 -0800
>
> x86: Default to ARCH=x86 to avoid overriding CONFIG_64BIT
>
> It is easy to waste a bunch of time when one takes a 32-bit .config
> from a test machine and try to build it on a faster 64-bit system, and
> its existing setting of CONFIG_64BIT=n gets *changed* to match the
> build host. Similarly, if one has an existing build tree it is easy
> to trash an entire build tree that way.
>
> This is because the default setting for $ARCH when discovered from
> 'uname' is one of the legacy pre-x86-merge values (i386 or x86_64),
> which effectively force the setting of CONFIG_64BIT to match. We should
> default to ARCH=x86 instead, finally completing the merge that we
> started so long ago.
Ok, I don't know whether this was on purpose or not but setting ARCH=x86
has the side effect of putting the config 64BIT prompt into the toplevel
menuconfig:
[*] 64-bit kernel
General setup --->
[*] Enable loadable module support --->
[*] Enable the block layer --->
Processor type and features --->
Now, IMHO, maybe the more fitting place for this should be "Processor
type and features" where all the arch-specific stuff goes but looking at
arch/x86/Kconfig, it would need some restructuring due to dependencies.
So how about we simply hide it by still preserving the functionality:
--
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 50b1b1bf442b..e8d7e9250853 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -1,6 +1,7 @@
# Select 32 or 64 bit
config 64BIT
- bool "64-bit kernel" if ARCH = "x86"
+ bool
+ default y if ARCH = "x86"
default ARCH != "i386"
---help---
Say yes to build a 64-bit kernel - formerly known as x86_64
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-01-12 17:06 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 21:51 [PATCH] x86: Default to ARCH=x86 " David Woodhouse
2012-12-21 2:07 ` [tip:x86/build] x86: Default to ARCH= x86 " tip-bot for David Woodhouse
2012-12-26 6:32 ` David Rientjes
2012-12-26 8:43 ` David Woodhouse
2012-12-26 10:44 ` David Rientjes
2012-12-26 12:38 ` David Woodhouse
2012-12-26 22:00 ` David Rientjes
2012-12-26 22:19 ` David Woodhouse
2012-12-27 1:52 ` David Rientjes
2012-12-27 8:01 ` David Woodhouse
2012-12-26 22:30 ` Jesper Juhl
2012-12-26 23:07 ` David Woodhouse
2012-12-26 23:13 ` H. Peter Anvin
2012-12-26 23:32 ` [tip] config: Add 'make kvmconfig' David Woodhouse
2012-12-27 1:08 ` Randy Dunlap
2013-02-04 18:20 ` [patch] config: fix make kvmconfig David Rientjes
2013-02-04 18:44 ` Ingo Molnar
2013-02-04 18:57 ` David Rientjes
2013-02-04 19:11 ` Ingo Molnar
2013-02-04 19:14 ` Greg Kroah-Hartman
2013-02-04 19:13 ` Ingo Molnar
2013-02-06 18:25 ` Pekka Enberg
2013-02-06 20:12 ` David Rientjes
2013-02-06 20:45 ` Pekka Enberg
2013-02-06 21:02 ` kvmtool tree (Was: Re: [patch] config: fix make kvmconfig) Stephen Rothwell
2013-02-06 21:46 ` Ingo Molnar
2013-02-06 21:55 ` H. Peter Anvin
2013-02-07 21:44 ` Stephen Rothwell
2013-02-07 21:40 ` Stephen Rothwell
2013-02-08 14:55 ` Ingo Molnar
2013-02-08 21:14 ` Linus Torvalds
2013-02-08 23:57 ` Pekka Enberg
2013-02-09 0:45 ` Linus Torvalds
2013-02-09 10:01 ` Pekka Enberg
2013-02-09 18:07 ` Linus Torvalds
2013-02-09 19:39 ` Pekka Enberg
2013-02-09 19:57 ` Linus Torvalds
2013-02-09 21:06 ` Theodore Ts'o
2013-02-11 12:38 ` Ingo Molnar
2013-02-11 12:26 ` Ingo Molnar
2013-02-11 12:56 ` Ingo Molnar
2013-02-11 13:18 ` David Woodhouse
2013-02-11 13:58 ` Anca Emanuel
2013-02-11 16:34 ` Linus Torvalds
2013-02-11 17:34 ` H. Peter Anvin
2013-02-11 17:41 ` Ingo Molnar
2013-02-11 14:47 ` Pekka Enberg
2013-02-11 16:46 ` David Woodhouse
2013-02-11 17:26 ` Anca Emanuel
2013-02-11 16:32 ` Linus Torvalds
2013-02-11 17:28 ` Ingo Molnar
[not found] ` <CA+55aFx-0-qcYMqH2wnJJ7iAPhoEvD_EQ0xqVW3VGS3G9=_1_w@mail.gmail.com>
2013-02-11 17:58 ` Ingo Molnar
2013-02-11 23:32 ` Linus Torvalds
2013-02-12 9:52 ` Ingo Molnar
2013-02-13 8:23 ` Paolo Bonzini
2013-02-13 8:56 ` Pekka Enberg
2013-02-13 9:23 ` Ingo Molnar
2013-02-14 15:32 ` Anthony Liguori
2013-02-19 8:08 ` Ingo Molnar
2013-01-12 17:06 ` Borislav Petkov [this message]
2013-01-12 17:40 ` [tip:x86/build] x86: Default to ARCH= x86 to avoid overriding CONFIG_64BIT H. Peter Anvin
2013-01-12 18:08 ` Borislav Petkov
2013-01-12 18:10 ` H. Peter Anvin
2013-04-12 16:01 ` [PATCH] x86: Default to ARCH=x86 " richard -rw- weinberger
2013-04-12 16:38 ` David Woodhouse
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=20130112170647.GA10659@liondog.tnic \
--to=bp@alien8.de \
--cc=David.Woodhouse@intel.com \
--cc=dwmw2@infradead.org \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.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
all inboxes | Powered by JetHome®