On Sun, Oct 21, 2012 at 01:29:35PM +0200, richard -rw- weinberger wrote:
> Every kernel developer has his own wrapper script to make qemu usable.
> IMHO it's time to add such a script to the kernel tree.
One observation I'll make is that for many people, what you want to do
is a *lot* more than just simply create a wrapper script to fire up
qemu. For me to do my testing, I want to build a kernel on the host
OS, and then fire up a script which fires up xfstests and runs it with
a collection of different file system mount options to do my ext4
testing. I've shared that here:
git://git.kernel.org/pub/scm/fs/ext2/xfstests-bld.git
where the host-side scripts are in the kvm-xfstests directory, and the
guest-side scripts are in the kvm-autorun directory. I can pass in a
set of fs configurations and xfstest test numbers via the command line
on the host os, i.e., "kvm-xfstests -c 4k,ext4,nojournal
13,225,245,246". And then afterwards the scripts parse out the test
output and summarizes so it's easy to see what passed and what failed.
So the bottom line is that for me at least, starting up qemu is a very
tiny part of what I need to do in order to do my testing. If you want
to really encourage good testing, what would be better is to encourage
more people to create standardized testing and benchmarking scripts
that many kernel developers can easily run. And those are going to be
complex enough that I don't think it makes sense for them to live in
the kernel tree.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
