All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Thumshirn <jthumshirn@suse.de>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH] test: add fio test for device-dax
Date: Thu, 30 Mar 2017 10:47:01 +0200	[thread overview]
Message-ID: <20170330084701.GA4027@linux-x5ow.site> (raw)
In-Reply-To: <x49efxfre00.fsf@segfault.boston.devel.redhat.com>

On Wed, Mar 29, 2017 at 05:04:31PM -0400, Jeff Moyer wrote:
> Well, the goal was to be somewhat smart about it, by not even trying to
> test things that aren't implemented or configured into the current
> kernel (such as device dax, for example).  Upon thinking about it
> further, I don't think that gets us very far.  However, that does raise
> a use case that is not distro-specific.  If you don't enable device dax,
> your test suite will still try to run those tests.  ;-)

I think I already suggested this some time ago, but again, can't we
make a syfs/debugfs/ioctl/whatever query to see what "features" are
available and check this instead of the kernel version in the test
suite? IIRC drm does similar things. Quoting from [1]:

"Have a clear way for userspace to figure out whether your new ioctl
or ioctl extension is supported on a given kernel. If you can't rely
on old kernels rejecting the new flags/modes or ioctls (since doing
that was botched in the past) then you need a driver feature flag or
revision number somewhere."

[1] http://blog.ffwll.ch/2013/11/botching-up-ioctls.html

Byte,
   Johannes

-- 
Johannes Thumshirn                                          Storage
jthumshirn@suse.de                                +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

  parent reply	other threads:[~2017-03-30  8:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28  4:03 [PATCH] test: add fio test for device-dax Dan Williams
2017-03-29 20:02 ` Jeff Moyer
2017-03-29 20:07   ` Dan Williams
2017-03-29 20:19     ` Jeff Moyer
2017-03-29 20:30       ` Dan Williams
2017-03-29 20:49         ` Jeff Moyer
2017-03-29 20:56           ` Dan Williams
2017-03-29 21:04             ` Jeff Moyer
2017-03-29 21:12               ` Dan Williams
2017-03-30  6:16                 ` Xiong Zhou
2017-03-30  8:09                   ` Eryu Guan
2017-03-31 15:50                     ` Dan Williams
2017-03-30  8:47               ` Johannes Thumshirn [this message]
2017-03-30 16:08         ` Linda Knippers
2017-03-30 16:56           ` Dan Williams
2017-03-30 17:06             ` Linda Knippers
2017-03-30 17:12               ` Dan Williams
2017-03-30 17:19                 ` Linda Knippers
2017-03-30 17:59                   ` Dan Williams

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=20170330084701.GA4027@linux-x5ow.site \
    --to=jthumshirn@suse.de \
    --cc=jmoyer@redhat.com \
    --cc=linux-nvdimm@lists.01.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.