LKML Archive on
help / color / mirror / Atom feed
From: Adrian Bunk <>
To: Sam Ravnborg <>
Cc: Ingo Molnar <>,,,,
Subject: Re: [2.6 patch] x86: allow 64bit setting in Kconfig
Date: Mon, 11 Feb 2008 19:30:26 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Feb 11, 2008 at 06:13:21PM +0100, Sam Ravnborg wrote:
> > In my experience there is no way for me to enable 64BIT without somehow 
> > manually fiddling with ARCH.
> > 
> > No matter whether it's menuconfig or oldconfig or whatever else.
> >From the patch description when ARCH=x86 were introduced:
>     # make {allno,allyes,allmod,rand}config [ARCH=...]
>     option \ host arch      | 32bit         | 64bit
>     =====================================================
>     ./.                     | 32bit         | 64bit
>     ARCH=x86                | 32bit         | 32bit
>     ARCH=i386               | 32bit         | 32bit
>     ARCH=x86_64             | 64bit         | 64bit
>     The general rule are that ARCH= and native architecture
>     takes precedence over the configuration.
>     So make ARCH=i386 [whatever] will always build a 32-bit
>     kernel no matter what the configuration says.
>     The configuration will be updated to 32-bit if it was
>     configured to 64-bit and the other way around.
>     This behaviour is consistent with previous behaviour so
>     no suprises here.
>     make ARCH=x86 will per default result in a 32-bit kernel
>     but as the only ARCH= value x86 allow the user to select
>     between 32-bit and 64-bit using menuconfig.
> So what you see is what was then discussed and considered
> optimal functionality.

What you describe differs vastly from what Ingo considers optimal and 
describes as seeing on his computer. Why does oldconfig preserve the 
32/64bit for him?

And the fact that kconfig does not let you choose the 32/64bit unless 
you explicitely set ARCH=x86 is for users simply confusing.

> We shall keep in mind the main target here is to keep
> peoples systems running as usual when they shift to
> the unified {32 bit / 64 bit} x86 arch.
> If you want anything changed then do this with respect to
> the intended behaviour as documented above and keep the
> setup used by our less kernel skilled testers in mind.
> And you do not belong to the "less kernel skilled"
> testers base.

Your table talks about {allno,allyes,allmod,rand}config, and this is 
definitely not stuff "less kernel skilled testers" should be using.

> 	Sam



       "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

      reply	other threads:[~2008-02-11 17:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28 22:09 Adrian Bunk
2008-02-01 15:22 ` Ingo Molnar
2008-02-04 20:45   ` Adrian Bunk
2008-02-11 16:37     ` Ingo Molnar
2008-02-11 16:50       ` Adrian Bunk
2008-02-11 17:13         ` Sam Ravnborg
2008-02-11 17:30           ` Adrian Bunk [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \
    --subject='Re: [2.6 patch] x86: allow 64bit setting in Kconfig' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).