From: Rusty Russell <rusty@rustcorp.com.au>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: fix pte_flags() to only return flags, fix lguest (updated)
Date: Wed, 23 Jul 2008 10:59:20 +1000 [thread overview]
Message-ID: <200807231059.20810.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20080722090432.GD2065@elte.hu>
On Tuesday 22 July 2008 19:04:32 Ingo Molnar wrote:
> i'm wondering. My randconfig tests boot up an lguest enabled kernel
> every 30 minutes or so:
>
> config-Mon_Jul_21_19_05_54_CEST_2008.good:CONFIG_LGUEST=y
> config-Mon_Jul_21_19_43_13_CEST_2008.good:CONFIG_LGUEST=y
> config-Mon_Jul_21_19_47_40_CEST_2008.good:CONFIG_LGUEST=y
> config-Mon_Jul_21_20_37_41_CEST_2008.good:CONFIG_LGUEST=y
> config-Mon_Jul_21_22_11_42_CEST_2008.good:CONFIG_LGUEST=y
> config-Mon_Jul_21_22_16_59_CEST_2008.good:CONFIG_LGUEST=y
> config-Mon_Jul_21_22_32_22_CEST_2008.good:CONFIG_LGUEST=y
> config-Mon_Jul_21_23_25_55_CEST_2008.good:CONFIG_LGUEST=y
> config-Mon_Jul_21_23_51_29_CEST_2008.good:CONFIG_LGUEST=y
>
> Would it be possible to have some really stupid lguest self-test which
> would complain spectacularly in the host kernel if it fails to reach
> some minimal user-space?
>
> Something that could be self-contained within a single bzImage. (i.e. it
> would contain a minimalistic image of some sort with a very minimalistic
> userspace component as well - or something like that)
Well, adding "make -C Documentation/lguest" to the build is a good start (this
finds those "e820.h not longer includable from userspace" bugs).
Secondly, if you put the resulting Documentation/lguest/lguest somewhere on
your booting test machine, it can just do something like
./lguest 64 /boot/vmlinuz-`uname -r` | grep 'VFS: Unable to mount root'
Won't quite test userspace, but it's easy and will get the worst breakage.
If we want to be more ambitious, I'd suggest a tiny initrd with a
statically-linked /hello_world to test userspace:
./lguest --initrd=/boot/hello_world.initrd 64 /boot/vmlinuz-`uname -r` \
rdinit=/hello_world | grep 'Hello world'
I can create one (and test the example) for you if you're interested?
Thanks,
Rusty.
next prev parent reply other threads:[~2008-07-23 2:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 4:31 [PATCH] x86: fix pte_flags() to only return flags, fix lguest Rusty Russell
2008-07-22 4:38 ` Stephen Rothwell
2008-07-22 4:51 ` Jeremy Fitzhardinge
2008-07-22 4:52 ` Rusty Russell
2008-07-22 4:49 ` Jeremy Fitzhardinge
2008-07-22 5:40 ` [PATCH] x86: fix pte_flags() to only return flags, fix lguest (updated) Rusty Russell
2008-07-22 5:59 ` [PATCH 1/2] x86: rename PTE_MASK to PTE_PFN_MASK Jeremy Fitzhardinge
2008-07-22 8:36 ` Ingo Molnar
2008-07-22 10:58 ` Rusty Russell
2008-07-22 11:55 ` Ingo Molnar
2008-07-22 13:03 ` Johannes Weiner
2008-07-22 14:52 ` Jeremy Fitzhardinge
2008-07-22 15:18 ` Johannes Weiner
2008-07-22 15:23 ` Johannes Weiner
2008-07-22 15:33 ` Ingo Molnar
2008-07-22 15:43 ` Johannes Weiner
2008-07-22 5:59 ` [PATCH 2/2] x86: add PTE_FLAGS_MASK Jeremy Fitzhardinge
2008-07-22 9:04 ` [PATCH] x86: fix pte_flags() to only return flags, fix lguest (updated) Ingo Molnar
2008-07-23 0:59 ` Rusty Russell [this message]
2008-07-24 11:31 ` Ingo Molnar
2008-07-25 1:55 ` Rusty Russell
2008-07-28 15:11 ` Ingo Molnar
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=200807231059.20810.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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