From: "Uladzislau Rezki (Sony)" <urezki@gmail.com>
To: Michal Hocko <mhocko@suse.com>, Kees Cook <keescook@chromium.org>,
Shuah Khan <shuah@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Oleksiy Avramchenko <oleksiy.avramchenko@sonymobile.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Uladzislau Rezki (Sony)" <urezki@gmail.com>
Subject: [RFC v2 0/3] test driver to analyse vmalloc allocator
Date: Mon, 31 Dec 2018 14:26:37 +0100 [thread overview]
Message-ID: <20181231132640.21898-1-urezki@gmail.com> (raw)
Hello.
The first RFC was here: https://lkml.org/lkml/2018/11/13/957
Please have a look there for detailed description and discussion.
Here i will just specify what has been done since last RFC:
Changes in v2:
- Code cleanup to make it more simple;
- Now __vmalloc_node_range() is exported if CONFIG_TEST_VMALLOC_MODULE=m
- Integrate vmalloc test suite into tools/testing/selftests/vm
I hope this test suite is more or less ready to go with. Appreciate your
comments and feedback anyway, so please RFC v2.
Thanks.
Uladzislau Rezks (Sony) (3):
vmalloc: export __vmalloc_node_range for CONFIG_TEST_VMALLOC_MODULE
vmalloc: add test driver to analyse vmalloc allocator
selftests/vm: add script helper for CONFIG_TEST_VMALLOC_MODULE
lib/Kconfig.debug | 12 +
lib/Makefile | 1 +
lib/test_vmalloc.c | 543 +++++++++++++++++++++++++++++
mm/vmalloc.c | 9 +
tools/testing/selftests/vm/run_vmtests | 11 +
tools/testing/selftests/vm/test_vmalloc.sh | 173 +++++++++
6 files changed, 749 insertions(+)
create mode 100644 lib/test_vmalloc.c
create mode 100755 tools/testing/selftests/vm/test_vmalloc.sh
--
2.11.0
next reply other threads:[~2018-12-31 13:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 13:26 Uladzislau Rezki (Sony) [this message]
2018-12-31 13:26 ` [RFC v2 1/3] vmalloc: export __vmalloc_node_range for CONFIG_TEST_VMALLOC_MODULE Uladzislau Rezki (Sony)
2018-12-31 18:50 ` Matthew Wilcox
2019-01-01 16:55 ` Uladzislau Rezki
2018-12-31 13:26 ` [RFC v2 2/3] vmalloc: add test driver to analyse vmalloc allocator Uladzislau Rezki (Sony)
2018-12-31 13:26 ` [RFC v2 3/3] selftests/vm: add script helper for CONFIG_TEST_VMALLOC_MODULE Uladzislau Rezki (Sony)
2018-12-31 17:47 ` shuah
2019-01-01 17:12 ` Uladzislau Rezki
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=20181231132640.21898-1-urezki@gmail.com \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=oleksiy.avramchenko@sonymobile.com \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--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