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] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0711140606430.1818@scrub.home>
Date:	Wed, 14 Nov 2007 21:13:52 +0100 (CET)
From:	Roman Zippel <zippel@...ux-m68k.org>
To:	Jeff Garzik <jeff@...zik.org>
cc:	Brian Gerst <bgerst@...ntduck.org>,
	Sam Ravnborg <sam@...nborg.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"

Hi,

On Fri, 9 Nov 2007, Jeff Garzik wrote:

> > > I switch between other cross-compiled arches (alpha, usually) on the
> > > makefile command line
> > > 
> > > Yes, I know other 32/64-bit arches require .config editing.  That
> > > doesn't change the basic fact that this is a workflow regression.
> > > 
> > >     Jeff
> > 
> > You can use:
> > 
> > make i386_defconfig
> > make x86_64_defconfig
> 
> Does that work for alpha too?
> 
> 
> > In any other case you'd be editing the .config anyways.
> 
> No, that's a logic rathole down which I will not follow :)
> 
> You can make any argument along those lines command line usage is really an
> art, not a science.  Its a user interface, and that involves human taste
> rather than logic.
> 
> I've been bouncing between architectures using ARCH= for years, and my fingers
> and brain have been trained.  It's just disappointing and a pain to change
> this nice user interface that has served so well for years.

I disagree that this is a regression. You can still bounce between archs 
as before, but the fact is that these are not separate archs anymore. The 
sooner we'll get used to the fact the better.
You also don't bounce between archs just by changing ARCH, you also have 
to reconfigure the kernel and that's there you can change the 64bit 
option. This means for the normal user not much is changing and from an 
experienced user I'd expect to know the difference.

If we look at this as a new feature, we have to look at what is needed to 
support this properly. Should the arch name imply certain config options? 
This wouldn't have to be limited to 64BIT - SMP or MMU could be other 
options. I think it would also make sense to hide the corresponding config 
option, otherwise one could change an option, which is a little later 
ignored anyway. Another question would be if and how it affects other 
information like uname information.

What I'd like to avoid is to add potential cruft, which is only used to 
avoid the inevitable to properly learn how to configure the kernel. A user 
interface has a lot to do with logic, especially consistency - an 
inconsistent mess also doesn't taste very good.

bye, Roman
-
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/