From: Richard Weinberger <richard@nod.at>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
Linux-Arch <linux-arch@vger.kernel.org>,
Michal Marek <mmarek@suse.cz>, Ralf Baechle <ralf@linux-mips.org>,
Paul Mundt <lethal@linux-sh.org>, Jeff Dike <jdike@addtoit.com>,
Guan Xuetao <gxt@mprc.pku.edu.cn>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
the arch/x86 maintainers <x86@kernel.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Linux MIPS Mailing List <linux-mips@linux-mips.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [PATCH 2/8] um: Do not use SUBARCH
Date: Thu, 26 Sep 2013 14:24:44 +0000 [thread overview]
Message-ID: <524443AC.3040409@nod.at> (raw)
In-Reply-To: <CAMuHMdU3LdDhbp_AKjD7b8Wytbqfp29DrPwTdtwQa2hUNdcy3Q@mail.gmail.com>
Am 26.09.2013 15:26, schrieb Geert Uytterhoeven:
> On Thu, Sep 26, 2013 at 3:13 PM, Ramkumar Ramachandra
> <artagnon@gmail.com> wrote:
>> 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.
>
> Sorry for chiming in, but... what about cross compiling?
> SUBARCH=x86 should give you a 32-bit ia32 kernel, right?
Correct.
Users expect from SUBARCH=x86 a i386 32bit UML kernel.
Thanks,
//richard
next prev parent reply other threads:[~2013-09-26 14:24 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 8:19 [RFC] Get rid of SUBARCH Richard Weinberger
2013-08-21 8:19 ` [PATCH 1/8] um: Create defconfigs for i386 and x86_64 Richard Weinberger
2013-08-22 4:55 ` Stephen Rothwell
2013-09-26 10:32 ` Ramkumar Ramachandra
2013-09-26 10:35 ` Richard Weinberger
2013-09-26 11:58 ` Ramkumar Ramachandra
2013-09-26 12:04 ` Richard Weinberger
2013-09-27 9:22 ` Toralf Förster
2013-09-27 9:26 ` Richard Weinberger
2013-08-21 8:19 ` [PATCH 2/8] um: Do not use SUBARCH Richard Weinberger
2013-09-26 10:52 ` Ramkumar Ramachandra
2013-09-26 10:44 ` Richard Weinberger
2013-09-26 10:54 ` Ramkumar Ramachandra
2013-09-26 11:01 ` Richard Weinberger
2013-09-26 11:55 ` Ramkumar Ramachandra
2013-09-26 11:56 ` Richard Weinberger
2013-09-26 12:12 ` Ramkumar Ramachandra
2013-09-26 13:25 ` Ramkumar Ramachandra
2013-09-26 13:26 ` Geert Uytterhoeven
2013-09-26 13:58 ` Ramkumar Ramachandra
2013-09-26 14:24 ` Richard Weinberger [this message]
2013-09-26 14:48 ` Ramkumar Ramachandra
2013-09-26 15:04 ` Richard Weinberger
2013-09-26 16:18 ` Ramkumar Ramachandra
2013-09-26 17:10 ` Richard Weinberger
2013-08-21 8:19 ` [PATCH 3/8] um: Remove old defconfig Richard Weinberger
2013-08-21 8:19 ` [PATCH 4/8] m68k: Do not use SUBARCH Richard Weinberger
2013-08-21 8:19 ` [PATCH 5/8] sh: " Richard Weinberger
2013-08-21 8:19 ` [PATCH 6/8] mips: " Richard Weinberger
2013-08-21 8:19 ` [PATCH 7/8] unicore32: " Richard Weinberger
2013-08-21 8:19 ` [PATCH 8/8] Makefile: Remove SUBARCH Richard Weinberger
2013-08-21 12:07 ` [RFC] Get rid of SUBARCH Geert Uytterhoeven
2013-08-21 12:16 ` Richard Weinberger
2013-08-21 17:25 ` Rob Landley
2013-08-21 19:51 ` Sam Ravnborg
2013-08-22 12:58 ` Geert Uytterhoeven
2013-08-22 20:41 ` Rob Landley
2013-08-22 20:55 ` David Daney
2013-08-22 21:32 ` Rob Landley
2013-08-21 12:53 ` Thorsten Glaser
2013-08-21 12:58 ` H. Peter Anvin
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=524443AC.3040409@nod.at \
--to=richard@nod.at \
--cc=artagnon@gmail.com \
--cc=geert@linux-m68k.org \
--cc=gxt@mprc.pku.edu.cn \
--cc=hpa@zytor.com \
--cc=jdike@addtoit.com \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-sh@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mmarek@suse.cz \
--cc=ralf@linux-mips.org \
--cc=tglx@linutronix.de \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).