From: Omar Sandoval <osandov@osandov.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: Linux Block Layer Mailinglist <linux-block@vger.kernel.org>,
Linux NVMe Mailinglist <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH blktests] Documentation: document prerequisite scriptlets
Date: Tue, 22 May 2018 17:15:30 -0700 [thread overview]
Message-ID: <20180523001530.GJ9536@vader> (raw)
In-Reply-To: <20180522073024.axmhji5nel7kx4tm@linux-x5ow.site>
On Tue, May 22, 2018 at 09:30:24AM +0200, Johannes Thumshirn wrote:
> On Mon, May 21, 2018 at 11:29:04AM -0700, Omar Sandoval wrote:
> > But I'm curious about this specific example. Is this not mounted for you
> > automatically? I'm guessing systemd does it for me on my setup.
>
> No my setup is kind of special. I don't want to mess with all the
> user-space so all I do is:
>
> dracut --no-compress --kver `make kernelrelease` --kmoddir mods/ \
> --no-hostonly --no-hostonly-cmdline --modules "bash base" \
> --tmpdir `pwd`/myinitrd --force myinitrd/initrd \
> --add-drivers "loop nvme nvme-loop nvmet" \
> --install "lsblk find sort parted getopt fio tput column date \
> dirname mktemp ps diff awk timeout time losetup \
> truncate wc grep stat basename cut blktrace sg_inq \
> realpath findmnt vi dd sed rm rmdir nvme" \
> --include "$HOME/src/blktests" "/blktests
>
> qemu-kvm -m 4096 -smp 4 -nographic -serial mon:stdio -kernel \
> arch/x86/boot/bzImage -initrd myinitrd/initrd \
> -append "console=ttyS0 debug"
>
> I have the above in a shell wrapper as I simply can't remember it, or
> I just use rapido [1] which a co-worker of mine started for this job.
>
> As minimal as possible. I try to get my rebuild - boot - test cycles
> short.
>
> With my current config I have a bootup time in qemu below half a
> second on a reasonable machine in my lab and just below one second
> on my laptop.
>
> [1] https://github.com/rapido-linux/rapido
>
> Byte,
> Johannes
Cool setup :) I have my own fanciness [1] which lets met boot straight
into a test kernel without packaging it up in any way.
Anyways, I added some documentation based on yours. Thanks!
1: https://github.com/osandov/osandov-linux#vm-setup
WARNING: multiple messages have this Message-ID (diff)
From: osandov@osandov.com (Omar Sandoval)
Subject: [PATCH blktests] Documentation: document prerequisite scriptlets
Date: Tue, 22 May 2018 17:15:30 -0700 [thread overview]
Message-ID: <20180523001530.GJ9536@vader> (raw)
In-Reply-To: <20180522073024.axmhji5nel7kx4tm@linux-x5ow.site>
On Tue, May 22, 2018@09:30:24AM +0200, Johannes Thumshirn wrote:
> On Mon, May 21, 2018@11:29:04AM -0700, Omar Sandoval wrote:
> > But I'm curious about this specific example. Is this not mounted for you
> > automatically? I'm guessing systemd does it for me on my setup.
>
> No my setup is kind of special. I don't want to mess with all the
> user-space so all I do is:
>
> dracut --no-compress --kver `make kernelrelease` --kmoddir mods/ \
> --no-hostonly --no-hostonly-cmdline --modules "bash base" \
> --tmpdir `pwd`/myinitrd --force myinitrd/initrd \
> --add-drivers "loop nvme nvme-loop nvmet" \
> --install "lsblk find sort parted getopt fio tput column date \
> dirname mktemp ps diff awk timeout time losetup \
> truncate wc grep stat basename cut blktrace sg_inq \
> realpath findmnt vi dd sed rm rmdir nvme" \
> --include "$HOME/src/blktests" "/blktests
>
> qemu-kvm -m 4096 -smp 4 -nographic -serial mon:stdio -kernel \
> arch/x86/boot/bzImage -initrd myinitrd/initrd \
> -append "console=ttyS0 debug"
>
> I have the above in a shell wrapper as I simply can't remember it, or
> I just use rapido [1] which a co-worker of mine started for this job.
>
> As minimal as possible. I try to get my rebuild - boot - test cycles
> short.
>
> With my current config I have a bootup time in qemu below half a
> second on a reasonable machine in my lab and just below one second
> on my laptop.
>
> [1] https://github.com/rapido-linux/rapido
>
> Byte,
> Johannes
Cool setup :) I have my own fanciness [1] which lets met boot straight
into a test kernel without packaging it up in any way.
Anyways, I added some documentation based on yours. Thanks!
1: https://github.com/osandov/osandov-linux#vm-setup
next prev parent reply other threads:[~2018-05-23 0:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 11:40 [PATCH blktests] Documentation: document prerequisite scriptlets Johannes Thumshirn
2018-05-14 11:40 ` Johannes Thumshirn
2018-05-17 13:44 ` Johannes Thumshirn
2018-05-17 13:44 ` Johannes Thumshirn
2018-05-21 18:29 ` Omar Sandoval
2018-05-21 18:29 ` Omar Sandoval
2018-05-22 7:30 ` Johannes Thumshirn
2018-05-22 7:30 ` Johannes Thumshirn
2018-05-23 0:15 ` Omar Sandoval [this message]
2018-05-23 0:15 ` Omar Sandoval
2018-05-23 7:23 ` Johannes Thumshirn
2018-05-23 7:23 ` Johannes Thumshirn
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=20180523001530.GJ9536@vader \
--to=osandov@osandov.com \
--cc=jthumshirn@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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 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.