Am 27.09.2013 11:22, schrieb Toralf Förster:
> On 09/26/2013 12:35 PM, Richard Weinberger wrote:
>> Am 26.09.2013 12:20, schrieb Ramkumar Ramachandra:
>>> Richard Weinberger wrote:
>>>> This patch is based on: https://lkml.org/lkml/2013/7/4/396
>>>>
>>>> Cc: Ramkumar Ramachandra <artag...@gmail.com>
>>>> Signed-off-by: Richard Weinberger <rich...@nod.at>
>>>> ---
>>>>  arch/um/configs/i386_defconfig   | 954 
>>>> +++++++++++++++++++++++++++++++++++++++
>>>>  arch/um/configs/x86_64_defconfig | 943 
>>>> ++++++++++++++++++++++++++++++++++++++
>>>>  2 files changed, 1897 insertions(+)
>>>>  create mode 100644 arch/um/configs/i386_defconfig
>>>>  create mode 100644 arch/um/configs/x86_64_defconfig
>>>
>>> First, I'm pissed that the upstream tree doesn't build and run out of
>>> the box months after I submitted a fix in July (and it's September
>>> now). Fact that you dropped my sane patches aside and decided to write
>>> a much larger series aside, user-mode Linux in upstream is broken.
>>> This means that any user who does:
>>>
>>> $ ARCH=um make defconfig
>>> $ ARCH=um make
>>>
>>> will end up with a *broken* Linux _today_. Unless the user is living
>>> in the Stone Age with a 32-bit computer, this is what she will see
>>> when she attempts to boot up Linux:
> 
> :-{
> 
> Grmpf
> 
> There are a lot of 32 bit user land linux installation (beside my own,
> look at the x86 Gentoo world) in the wild - even running on modern 64bit
> CPUs. The simple reason is that those installations run fine and the
> performance "boost" of 64bit often isn't worth a new reinstallation.

You *can* of course run 32bit userland on UML. Just create a 32bit UML on 
x86_64.

make defconfig ARCH=um SUBARCH=i386
make linux ARCH=um SUBARCH=i386

This will work on x86_64 and x86 hosts.

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

Reply via email to