linux-kernel - Re: [PATCH 0/11 v3] enable "make ARCH=x86"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 10 Nov 2007 10:21:41 +0100
From:	Adrian Bunk <bunk@...nel.org>
To:	Paul Mundt <lethal@...ux-sh.org>, Sam Ravnborg <sam@...nborg.org>,
	Jeff Garzik <jeff@...zik.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 0/11 v3] enable "make ARCH=x86"

On Sat, Nov 10, 2007 at 05:21:52PM +0900, Paul Mundt wrote:
> On Sat, Nov 10, 2007 at 08:54:44AM +0100, Sam Ravnborg wrote:
> > On Fri, Nov 09, 2007 at 10:23:23PM -0500, Jeff Garzik wrote:
> > > Sam Ravnborg wrote:
> > > >This is the patch that get rid of ARCH=i386 and ARCH=x86_64
> > > >and introduce ARCH=x86.
> > > >It touches several files but the changes are all one or two-liners.
> > > >
> > > >      x86: drop backward compatibility symlinks to i386/boot and 
> > > >      x86_64/boot
> > > >      kbuild: sanity check the specified arch
> > > 
> > > 
> > > IMO it negatives impacts the workflow when you -remove- the ability to 
> > > set 32/64-bit on the make command line.
> > > 
> > > Building and testing for both architectures now requires the additional 
> > > step of editing .config, which is a clear workflow negative impact at 
> > > least for me.
> > When it was decided to unify i386 and x86_64 it was at the same time
> > decided to handle them as a *single* architecture.
> > 
> > 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.
> 
> If you do that, then things like randconfigs will randomly break if you
> happen to use a toolchain targetted specifically at i386 or so.
>...

If you want to know how to restrict randconfig to CONFIG_X86_32 with an 
unified architecture you should either read the toplevel README in the 
kernel sources or an older email of mine in this thread...

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/