From: Linda Knippers <linda.knippers@hpe.com>
To: Dan Williams <dan.j.williams@intel.com>, 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 12:08:19 -0400 [thread overview]
Message-ID: <58DD2D73.9040902@hpe.com> (raw)
In-Reply-To: <CAPcyv4jsJZih6t_hQ2Y3T8n0cGh79Kjf98WHfK0xoTVuifrTUQ@mail.gmail.com>
On 03/29/2017 04:30 PM, Dan Williams wrote:
> On Wed, Mar 29, 2017 at 1:19 PM, Jeff Moyer <jmoyer@redhat.com> wrote:
>> Dan Williams <dan.j.williams@intel.com> writes:
>>
>>> On Wed, Mar 29, 2017 at 1:02 PM, Jeff Moyer <jmoyer@redhat.com> wrote:
>>>> Dan Williams <dan.j.williams@intel.com> writes:
>>>>
>>>>> +check_min_kver()
>>>>> +{
>>>>> + local ver="$1"
>>>>> + : "${KVER:=$(uname -r)}"
>>>>> +
>>>>> + [ -n "$ver" ] || return 1
>>>>> + [[ "$ver" == "$(echo -e "$ver\n$KVER" | sort -V | head -1)" ]]
>>>>> +}
>>>>> +
>>>>> +check_min_kver "4.11" || { echo "kernel $KVER may lack latest device-dax fixes"; exit $rc; }
>>>>
>>>> Can we stop with this kernel version checking, please? Test to see if
>>>> you can create a device dax instance. If not, skip the test. If so,
>>>> and if you have a kernel that isn't fixed, so be it, you'll get
>>>> failures.
>>>
>>> I'd rather not. It helps me keep track of what went in where. If you
>>> want to run all the tests on a random kernel just do:
>>>
>>> KVER="4.11.0" make check
>>
>> This, of course, breaks completely with distro kernels.
>
> Why does this break distro kernels? The KVER variable overrides "uname -r"
FYI - dax-errors.sh doesn't look at KVER.
-- ljk
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2017-03-30 16:09 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
2017-03-30 16:08 ` Linda Knippers [this message]
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=58DD2D73.9040902@hpe.com \
--to=linda.knippers@hpe.com \
--cc=dan.j.williams@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox