From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Boot all yes config kernel with QEMU
Date: Tue, 23 Oct 2018 09:36:22 +0100 [thread overview]
Message-ID: <20181023083622.GA32532@kroah.com> (raw)
In-Reply-To: <20181023061642.GE9944@eros>
On Tue, Oct 23, 2018 at 05:16:42PM +1100, Tobin C. Harding wrote:
> On Tue, Oct 23, 2018 at 12:22:44AM -0400, valdis.kletnieks at vt.edu wrote:
> > On Tue, 23 Oct 2018 13:56:42 +1100, "Tobin C. Harding" said:
> >
> > > I'd like to build and boot an allyesconfig kernel with QEMU. Building
> > > is no problem but when I try to boot it I get problems because the host
> > > system does not support features requested by the VM.
> > >
> > > How does one go about testing an allyesconfig kernel?
> >
> > As you have noticed, there's no guarantee that a allyesconfig kernel will boot in
> > a VM because the VM doesn't support something. Note that you're going to have
> > the exact same issues booting on real hardware - you'll discover that there's configs
> > that won't boot on real hardware either - and even if it boots, you'll probably not have
> > the I/O devices to test even a third of the drivers unless you have a really well stocked
> > test lab.
> >
> > But then, all(yes|mod|no)config aren't intended for actual booting and testing - they're
> > pretty much build testing all the options in one build.
> >
> > Basically, one of two things happen after building an all-something-config:
> >
> > 1) The build completes and you get on with your life
> >
> > 2) The build fails, and you get to send an email telling the maintainer that
> > their driver for the Frobnozz 1300 Widget won't build in =y in kernel 4.21-rc2,
> > or whatever your build died on.
>
> I love this answer :) thanks Valdis. If you are taking a walk and feel
> like pondering something; any ideas how I could get the most files
> possible to show up in /proc and /sys?
It all depends on your hardware/system. /sys reflects the devices in
the system at the time, physical and virtual.
If you create 20000 virtual scsi devices, you will have 20000 devices in
sysfs along with all of their assorted files and directories. People
have used virtual devices to stress-test sysfs since the very beginning.
Hope this helps,
greg k-h
prev parent reply other threads:[~2018-10-23 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 2:56 Boot all yes config kernel with QEMU Tobin C. Harding
2018-10-23 4:22 ` valdis.kletnieks at vt.edu
2018-10-23 6:16 ` Tobin C. Harding
2018-10-23 8:36 ` Greg KH [this message]
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=20181023083622.GA32532@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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).