linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
	xfs <linux-xfs@vger.kernel.org>,
	fstests@vger.kernel.org, Amir Goldstein <amir73il@gmail.com>,
	Sasha Levin <Alexander.Levin@microsoft.com>,
	Sasha Levin <levinsasha928@gmail.com>,
	Valentin Rothberg <valentinrothberg@gmail.com>,
	Ross Zwisler <ross.zwisler@linux.intel.com>,
	Kent Overstreet <kent.overstreet@gmail.com>,
	Brendan Higgins <brendanhiggins@google.com>
Subject: Re: [ANN] oscheck: wrapper for fstests check.sh - tracking and working with baselines
Date: Mon, 3 Dec 2018 15:41:12 -0800	[thread overview]
Message-ID: <20181203234112.GP28501@garbanzo.do-not-panic.com> (raw)
In-Reply-To: <20180714222115.GA13230@bombadil.infradead.org>

On Sat, Jul 14, 2018 at 03:21:15PM -0700, Matthew Wilcox wrote:
> On Fri, Jul 13, 2018 at 01:59:31PM -0700, Luis R. Chamberlain wrote:
> > > The best I've been able to
> > > do is now merged into Kent's ktest -- but you're not based on that,
> > > so I'll try and get your ostest set up to work with DAX.  Or maybe Ross
> > > can do it since he's actually been able to get 2MB pages working and I
> > > still haven't :-(
> > 
> > Patches and new sections to cover more ground indeed are appreciated!
> 
> I feel like we need to merge ktest and oscheck.  oscheck assumes that you
> know how to set up qemu, and ktest takes care of setting up qemu for you.
> I think it might be possible to turn oscheck into a set of ktest
> tests.

Everyone uses their own qemu based solution, it just so happens that I was
also not satisfied with what I saw and wrote my own solution, kvm-boot [0].

I'm sure others use other things too.

But... a qemu-less solution for a lot of tests would be great as well,
and for this I believe kunit [1] seems to be like a great possibility worth
exploring in the future.

[0] https://gitlab.com/mcgrof/kvm-boot
[1] https://patchwork.kernel.org/patch/10704147/

  Luis

  reply	other threads:[~2018-12-03 23:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-13  2:43 [ANN] oscheck: wrapper for fstests check.sh - tracking and working with baselines Luis R. Chamberlain
2018-07-13  8:39 ` Amir Goldstein
2018-07-13 16:44   ` Luis R. Chamberlain
2018-07-13 17:46     ` Luis R. Chamberlain
2018-07-13 20:40     ` Jeff Mahoney
2018-07-13 20:50       ` Luis R. Chamberlain
2018-07-13 21:03         ` Jeff Mahoney
2018-07-14  0:52     ` Theodore Y. Ts'o
2018-07-14  6:56     ` Eryu Guan
2018-07-13 20:51 ` Matthew Wilcox
2018-07-13 20:59   ` Luis R. Chamberlain
2018-07-14 22:21     ` Matthew Wilcox
2018-12-03 23:41       ` Luis Chamberlain [this message]
2018-12-04 11:01       ` Kent Overstreet
2019-08-16 17:34       ` Luis Chamberlain

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=20181203234112.GP28501@garbanzo.do-not-panic.com \
    --to=mcgrof@kernel.org \
    --cc=Alexander.Levin@microsoft.com \
    --cc=amir73il@gmail.com \
    --cc=brendanhiggins@google.com \
    --cc=fstests@vger.kernel.org \
    --cc=kent.overstreet@gmail.com \
    --cc=levinsasha928@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=ross.zwisler@linux.intel.com \
    --cc=valentinrothberg@gmail.com \
    --cc=willy@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 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).