From: Mike Kravetz <mike.kravetz@oracle.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
joern@purestorage.com
Cc: Davidlohr Bueso <dave@stgolabs.net>,
David Rientjes <rientjes@google.com>,
Mike Kravetz <mike.kravetz@oracle.com>
Subject: [PATCH 0/3] vm hugetlb selftest cleanup
Date: Thu, 30 Jul 2015 17:59:50 -0700 [thread overview]
Message-ID: <1438304393-30413-1-git-send-email-mike.kravetz@oracle.com> (raw)
As a followup to discussions of hugetlbfs fallocate, this provides
cleanup the vm hugetlb selftests. Remove hugetlbfstest as it tests
functionality not present in the kernel. Emphasize that libhugetlbfs
test suite should be used for hugetlb regression testing.
Mike Kravetz (3):
Reverted "selftests: add hugetlbfstest"
selftests:vm: Point to libhugetlbfs for regression testing
Documentation: update libhugetlbfs location and use for testing
Documentation/vm/hugetlbpage.txt | 15 ++++--
tools/testing/selftests/vm/Makefile | 2 +-
tools/testing/selftests/vm/hugetlbfstest.c | 86 ------------------------------
tools/testing/selftests/vm/run_vmtests | 13 ++---
4 files changed, 15 insertions(+), 101 deletions(-)
delete mode 100644 tools/testing/selftests/vm/hugetlbfstest.c
--
2.1.0
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2015-07-31 1:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 0:59 Mike Kravetz [this message]
2015-07-31 0:59 ` [PATCH 1/3] Reverted "selftests: add hugetlbfstest" Mike Kravetz
2015-08-04 3:57 ` Mike Kravetz
2015-07-31 0:59 ` [PATCH 2/3] selftests:vm: Point to libhugetlbfs for regression testing Mike Kravetz
2015-07-31 0:59 ` [PATCH 3/3] Documentation: update libhugetlbfs location and use for testing Mike Kravetz
2015-08-04 3:04 ` [PATCH 0/3] vm hugetlb selftest cleanup Naoya Horiguchi
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=1438304393-30413-1-git-send-email-mike.kravetz@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=dave@stgolabs.net \
--cc=joern@purestorage.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
/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).