[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190102085924.14145-1-urezki@gmail.com>
Date: Wed, 2 Jan 2019 09:59:21 +0100
From: "Uladzislau Rezki (Sony)" <urezki@...il.com>
To: Michal Hocko <mhocko@...e.com>, Kees Cook <keescook@...omium.org>,
Shuah Khan <shuah@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org
Cc: LKML <linux-kernel@...r.kernel.org>,
Matthew Wilcox <willy@...radead.org>,
Oleksiy Avramchenko <oleksiy.avramchenko@...ymobile.com>,
Thomas Gleixner <tglx@...utronix.de>,
"Uladzislau Rezki (Sony)" <urezki@...il.com>
Subject: [RFC v3 0/3] test driver to analyse vmalloc allocator
Hello.
This is v3.
The first RFC was here: https://lkml.org/lkml/2018/11/13/957
Please have a look there for detailed description and discussion.
Changes in v3:
- Export __vmalloc_node_range() with _GPL-only prefix;
- Add skip cases if the test can not be executed in current environment.
That is kselftest framework requirement.
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
Appreciate your comments and feedback, so please RFC v3.
Thank you.
Uladzislau Rezki (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 | 16 +
tools/testing/selftests/vm/test_vmalloc.sh | 176 ++++++++++
6 files changed, 757 insertions(+)
create mode 100644 lib/test_vmalloc.c
create mode 100755 tools/testing/selftests/vm/test_vmalloc.sh
--
2.11.0
Powered by blists - more mailing lists