From: Richard Weinberger <richard@nod.at>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: linux-arch@vger.kernel.org, "Michal Marek" <mmarek@suse.cz>,
geert@linux-m68k.org, ralf@linux-mips.org, 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>,
x86@kernel.org, linux-kbuild@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
linux-m68k@lists.linux-m68k.org, linux-mips@linux-mips.org,
linux-sh@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net,
"Toralf Förster" <toralf.foerster@gmx.de>
Subject: Re: [PATCH 1/8] um: Create defconfigs for i386 and x86_64
Date: Thu, 26 Sep 2013 12:04:53 +0000 [thread overview]
Message-ID: <524422E5.9080203@nod.at> (raw)
In-Reply-To: <CALkWK0nEy90VrWawTpYsLNJcnyRSizgArCa-qnzpuJQkyK6zHA@mail.gmail.com>
Am 26.09.2013 13:57, schrieb Ramkumar Ramachandra:
> Richard Weinberger wrote:
>>> $ file linux
>>> linux: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
>>> dynamically linked (uses shared libs), for GNU/Linux 2.6.32, not
>>> stripped
>>> $ ./linux ubd0=busybox-rootfs
>>> [...]
>>> Kernel panic - not syncing: No init found. Try passing init= option
>>> to kernel. See Linux Documentation/init.txt for guidance.
>>
>> I don't know that rootfs but it looks like there is no init.
>
> Ofcourse there's an init on the busybox-rootfs, and I'm able to boot
> it with an x86_64 Linux. The reason for panic is incorrect: I think
> (although not sure) a 32-bit rootfs userland will work.
A 32Bit UML kernel can run 32Bit users, a 64Bit UML kernel can only
run 64Bit userland. We have no 32Bit compat layer on x86_64.
Patches are welcome.
>>> [1] 25526 abort (core dumped) linux ubd0=busybox-rootfs
>>> %
>>>
>>> Rubbish.
>>
>> UML core dumps at panic() by design.
>
> On a related note, why does it screw up my terminal? I have to `reset`
> to get a nice working terminal.
I really don't know. That is not by design.
>> Seriously, my plan is to get rid of SUBARCH, that's why I did not push your patches
>> upstream and I've send the rid of SUBARCH patch series.
>> It turned out that other archs depend on SUBARCH too therefore some more thinking is needed.
>> Time passed, merge window closed, $dayjob needed some attention...
>
> Don't let some grand plan stall reasonable patches that fix immediate problems.
>
>> That said, your "arch/um: make it work with defconfig and x86_64" patch is also not perfect.
>> "make defconfig ARCH=um SUBARCH=x86" will create x86_64 defconfig, which is wrong and breaks existing
>> setups.
>
> Wrong.
>
> $ make defconfig ARCH=um SUBARCH=i386
> *** Default configuration is based on 'i386_defconfig'
> #
> # configuration written to .config
> #
I wrote "SUBARCH=x86" *not* SUBARCH=i386.
Again, if SUBARCH=x86 works too I'll happily merge it.
But as of now it breaks existing setups.
Thanks,
//richard
next prev parent reply other threads:[~2013-09-26 12:04 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 [this message]
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
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=524422E5.9080203@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=toralf.foerster@gmx.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).