From: Theodore Ts'o <tytso@mit.edu>
To: Nikhilesh Reddy <reddyn@codeaurora.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Running XFS tests on qemu
Date: Fri, 23 Oct 2015 05:34:28 -0400 [thread overview]
Message-ID: <20151023093428.GA7917@thunk.org> (raw)
In-Reply-To: <5629D4CE.2070400@codeaurora.org>
On Thu, Oct 22, 2015 at 11:33:50PM -0700, Nikhilesh Reddy wrote:
> Hi Ted
>
> Can you please help point me to instructions to setup and run xfs tests for
> ext4 to run on a local qemu installation from scratch?
https://git.kernel.org/cgit/fs/ext2/xfstests-bld.git/tree/quick-start?h=META
I haven't tried to make this work for qemu for arm (which I assume
you'd be more interested in), but if you do, please let me know. Also
note that I *do* have changes to build xfstests for android / bionic.
The build infrastructure is in the xfstests-bld git tree; however,
some of the changes to xfstests and xfsprogs haven't been accepted
upstream yet, but let me know if you are interested and I'll get you
the patches that haven't yet been accepted.
What's missing is the automation to talk to an Android device; I
ultimately fixed the bug I was chasing via other means.
(Unfortunately the USB-C device that was supposedly able to power a
Macbook Pro as well as connecting to a USB-attached SSD didn't work
against a Nexus 5X, and so I never finished getting xfstests running
on Android, although 95% of the work should be done.).
The two other missing pieces was getting upstream fio working on
Android/bionic (although there is a fio is the AOSP tree which should
work), and IIRC there were one or two fixup patches that I needed
against the bleeding-edge tip of coreutils so it would work with the
latest Android NDK. They were pretty obvious, but if you want I can
dig up the changes from my tree.
Finally, if you are doing x86-based development, you might be
interested in using Google Compute Engine to run your tests. I do
must of my testinng on GCE these days, beacuse it's much faster and I
can run multiple tests in parallel.
https://git.kernel.org/cgit/fs/ext2/xfstests-bld.git/tree/kvm-xfstests/README.GCE
Cheers,
- Ted
next prev parent reply other threads:[~2015-10-23 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 23:17 Using Cache barriers in lieu of REQ_FLUSH | REQ_FUA for emmc 5.1 (jdec spec JESD84-B51) Nikhilesh Reddy
2015-09-20 3:42 ` Theodore Ts'o
2015-09-28 22:28 ` Nikhilesh Reddy
2015-10-23 6:33 ` Running XFS tests on qemu Nikhilesh Reddy
2015-10-23 9:34 ` Theodore Ts'o [this message]
2015-10-27 17:55 ` Nikhilesh Reddy
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=20151023093428.GA7917@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=reddyn@codeaurora.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.