* Boot all yes config kernel with QEMU @ 2018-10-23 2:56 Tobin C. Harding 2018-10-23 4:22 ` valdis.kletnieks at vt.edu 0 siblings, 1 reply; 4+ messages in thread From: Tobin C. Harding @ 2018-10-23 2:56 UTC (permalink / raw) To: kernelnewbies Hi, 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? Back story: I'm trying to set up some CI infrastructure to run scripts/leaking_addresses.pl against the various stable kernels. thanks, Tobin. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20181023/0d83161e/attachment.sig> ^ permalink raw reply [flat|nested] 4+ messages in thread
* Boot all yes config kernel with QEMU 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 0 siblings, 1 reply; 4+ messages in thread From: valdis.kletnieks at vt.edu @ 2018-10-23 4:22 UTC (permalink / raw) To: kernelnewbies 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. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 486 bytes Desc: not available URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20181023/c42f2940/attachment.sig> ^ permalink raw reply [flat|nested] 4+ messages in thread
* Boot all yes config kernel with QEMU 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 0 siblings, 1 reply; 4+ messages in thread From: Tobin C. Harding @ 2018-10-23 6:16 UTC (permalink / raw) To: kernelnewbies 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? thanks, Tobin. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20181023/d8d8f8a4/attachment.sig> ^ permalink raw reply [flat|nested] 4+ messages in thread
* Boot all yes config kernel with QEMU 2018-10-23 6:16 ` Tobin C. Harding @ 2018-10-23 8:36 ` Greg KH 0 siblings, 0 replies; 4+ messages in thread From: Greg KH @ 2018-10-23 8:36 UTC (permalink / raw) To: kernelnewbies 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-10-23 8:36 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 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 is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.