[Top] [All Lists]

Re: [PATCH 2/8] um: Do not use SUBARCH

To: Richard Weinberger <>
Subject: Re: [PATCH 2/8] um: Do not use SUBARCH
From: Ramkumar Ramachandra <>
Date: Thu, 26 Sep 2013 18:43:16 +0530
Cc:, Michal Marek <>,,,, Jeff Dike <>, Guan Xuetao <>, Thomas Gleixner <>, Ingo Molnar <>, "H. Peter Anvin" <>,,, LKML <>,,,,
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=iio4Rr30IHGThubCmiGm13OO3dbs/OvbpdMbc+ORgaI=; b=zKxodCWv0rUGoBJdzOKpT1M9q+TezC6N4UacKpJtvs5IaTKGieGQka7Dz9jxThlheZ h8e1sUvki1YSMRyYZoc08qQXG38VptD8bl+zhwH3I3PvSxEcV9lxrGInKAMnPzYwIMgF tX35YmVXy3h3a1VUj7inAmE7Modt2sCCxk44sxLftb7KAtu08QxOGxQq0k6z4qeD2amg CrHo4M4uIZXEuqyAwCH1qYt4tJQraw0bj3uYY5tsrZMvffbOFLDdYZmmOQjYTrpsFr9m moIIPW8+cGuYwAjFkbxyhv7TfRz5QODQjwjVnbetIZ8C1mIb5GKwPswfnzD3Ik815AGR XPKQ==
In-reply-to: <>
List-archive: <>
List-help: <>
List-id: linux-mips <>
List-owner: <>
List-post: <>
List-software: Ecartis version 1.0.0
List-subscribe: <>
List-unsubscribe: <>
Original-recipient: rfc822;
References: <> <> <> <> <> <> <> <> <>
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.

<Prev in Thread] Current Thread [Next in Thread>