From: Dan Williams <dan.j.williams@intel.com>
To: linux-nvdimm@lists.01.org
Subject: [ndctl PATCH 0/4] test/dax.sh: Add huge page fault validation
Date: Sat, 19 Oct 2019 09:39:38 -0700 [thread overview]
Message-ID: <157150317870.3940762.5638079137146963300.stgit@dwillia2-desk3.amr.corp.intel.com> (raw)
v5.3 regressed huge page faulting and the ndctl unit test that tries to
generate huge page faults did not report it.
- Use trace-cmd to validate fault results
- Workaround XFS issues with fallocate > agsize
- Split the test to get distinct ext4 and xfs results
- Other misc fixups.
---
Dan Williams (4):
test/dax.sh: Fix failure reporting / handling
test/dax.sh: Fix xfs 2M alignment
test/dax.sh: Validate huge page mappings
test/dax.sh: Split into ext4 and xfs tests
test/Makefile.am | 3 +
test/dax-ext4.sh | 1
test/dax-pmd.c | 3 +
test/dax-xfs.sh | 1
test/dax.sh | 127 ++++++++++++++++++++++++++++++++++--------------------
5 files changed, 87 insertions(+), 48 deletions(-)
create mode 120000 test/dax-ext4.sh
create mode 120000 test/dax-xfs.sh
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
next reply other threads:[~2019-10-19 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-19 16:39 Dan Williams [this message]
2019-10-19 16:39 ` [ndctl PATCH 1/4] test/dax.sh: Fix failure reporting / handling Dan Williams
2019-10-19 16:39 ` [ndctl PATCH 2/4] test/dax.sh: Fix xfs 2M alignment Dan Williams
2019-10-19 16:39 ` [ndctl PATCH 3/4] test/dax.sh: Validate huge page mappings Dan Williams
2019-10-23 19:33 ` Verma, Vishal L
2019-10-23 19:41 ` Verma, Vishal L
2019-10-25 22:44 ` Verma, Vishal L
2019-10-25 23:26 ` Dan Williams
2019-10-19 16:39 ` [ndctl PATCH 4/4] test/dax.sh: Split into ext4 and xfs tests 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=157150317870.3940762.5638079137146963300.stgit@dwillia2-desk3.amr.corp.intel.com \
--to=dan.j.williams@intel.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;
as well as URLs for NNTP newsgroup(s).