[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALkWK0ndMtyQxE0uK4H-Ly6oy+tRn-SFc=_1WoC2QAp2uy0dtw@mail.gmail.com>
Date: Thu, 26 Sep 2013 18:43:16 +0530
From: Ramkumar Ramachandra <artagnon@...il.com>
To: Richard Weinberger <richard@....at>
Cc: linux-arch@...r.kernel.org, Michal Marek <mmarek@...e.cz>,
geert@...ux-m68k.org, ralf@...ux-mips.org, lethal@...ux-sh.org,
Jeff Dike <jdike@...toit.com>,
Guan Xuetao <gxt@...c.pku.edu.cn>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
linux-kbuild@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
linux-m68k@...ts.linux-m68k.org, linux-mips@...ux-mips.org,
linux-sh@...r.kernel.org,
user-mode-linux-devel@...ts.sourceforge.net
Subject: Re: [PATCH 2/8] um: Do not use SUBARCH
Ramkumar Ramachandra wrote:
> Richard Weinberger wrote:
>> I told you already that "make defconfig ARCH=um SUBARCH=x86" will spuriously
>> create a x86_64 config on x86_64.
>> This breaks existing setups.
>
> I'll fix this and resubmit soon.
Wait a minute. You're now arguing about whether the generic "x86"
means i386 or x86_64. Its meaning is already defined in
arch/x86/Kconfig and arch/x86/um/Kconfig: see the config 64BIT. Unless
i386 is explicitly specified, the default is to build a 64-bit kernel.
That is already defined for a normal Linux kernel, and user-mode Linux
should not break that convention. So, in the example you pulled out of
your hat:
$ make defconfig ARCH=um SUBARCH=x86
the user should expect a 64-bit build, and not an i386 build as you
say. Both my patches are correct, and the "regression" that you
pointed out is a red herring.
--
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/
Powered by blists - more mailing lists