From: Theodore Ts'o <tytso@mit.edu>
To: linux-ext4@vger.kernel.org
Cc: mhalcrow@google.com
Subject: Updated version of kvm-xfstests available
Date: Sun, 7 Sep 2014 22:01:01 -0400 [thread overview]
Message-ID: <20140908020101.GD1066@thunk.org> (raw)
In-Reply-To: <20140809234556.GA11072@thunk.org>
I've uploaded a new set of precompiled kvm-xfstests test appliances
at:
https://www.kernel.org/pub/linux/kernel/people/tytso/kvm-xfstests
This new version has an updated xfstests with a few more tests
enabled. It also features the ability for you to telnet to localhost
ports 7500, 7501, and 7502 and get shell prompts while the tests are
running (if you want to check on /proc/slabinfo, enable tracing, etc.)
You can also access the qemu monitor on port 7498, and you debug the
kernel using remote gdb on localhost port 7499. Just run "gdb
/path/to/vmlinux", and then use the command "target remote
localhost:7499". (Pro tip: it's helpful to temporarily add
"EXTRA_CFLAGS += -O0" to fs/{ext4,jbd2}/Makefile, and to make sure you
have CONFIG_DEBUG_INFO, CONFIG_DEBUG_INFO_DWARF4, and
CONFIG_FRAME_POINTER enabled.)
There are a few more options which kvm-xfstests supports, so you can
configure the number of cpus, add additional mount options, etc.
There is also an improved help message, which should explain all of
this and make it much more user-friendly: "./kvm-xfstests help"
Finally, I've added support to help run tests on Michael Halcrow's
encryption patches. To run it, make sure you have the unstable branch
of the ext4.git tree, which includes some fixes since the last version
he posted, and support for the dummy_encryption mount option. Then
run the command "./kvm-xfstests -c encrypt -m nodelalloc -g auto".
If you have a local git repository of xfstests-bld, make sure you do a
"git pull" to update the latest version of the kvm-xfstests shell
script. If you download the root_fs.img file from www.kernel.org, you
won't have build xfstests on your own. Just drop the root_fs.img file
in kvm-xfstests/test-appliance, look at kvm-xfstests/config and
override various parameters using ~/.config/kvm-xfstests or in the
kvm-xfstests/config.custom file. When you're ready, cd into the
kvm-xfstests directory, and then run "./kvm-xfstests smoke" and make
sure everything works.
Enjoy, and have fun!!
- Ted
P.S. If you want to run tests by hand, perhaps because you want to
set up a debug environment do some ftrace setups first, run
"./kvm-xfstests shell", then in the guest shell prompt, run the
command ". test-env". Then override the environment variables
FSTESTCFG and FSTESTSET (for example: FSTESTCFG=data_journal;
FSTESTSET="ext4/001 generic/013" or FSTESTSET="-g quick"), and then
run the shell script "./runtests.sh"
next prev parent reply other threads:[~2014-09-08 2:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 23:45 Updated versoin of kvm-xfstests available Theodore Ts'o
2014-08-12 16:08 ` Updated version " Theodore Ts'o
2014-08-12 16:10 ` Theodore Ts'o
2014-08-12 16:10 ` Theodore Ts'o
2014-08-23 17:35 ` Eric Whitney
2014-09-08 2:01 ` Theodore Ts'o [this message]
2014-10-28 15:20 ` Theodore Ts'o
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=20140908020101.GD1066@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=mhalcrow@google.com \
/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).