[RFC,v4,0/3] test driver to analyse vmalloc allocator

Message

Uladzislau Rezki Jan. 3, 2019, 2:21 p.m. UTC

Hello.

This is v4. I think it is ready to go with, unless there are extra requests
or comments.

Changes in v4:
    - Since the test can take time, switch to wait_for_completion_timeout()
      with HZ sleep interval to prevent triggering of the trace about hung
      task;
    - Fix clean apply for v4.20 kernel.

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

I think it is ready to go with, unless there are more requests or comments.

Thank you in advance.

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                         | 548 +++++++++++++++++++++++++++++
 mm/vmalloc.c                               |   9 +
 tools/testing/selftests/vm/run_vmtests     |  16 +
 tools/testing/selftests/vm/test_vmalloc.sh | 176 +++++++++
 6 files changed, 762 insertions(+)
 create mode 100644 lib/test_vmalloc.c
 create mode 100755 tools/testing/selftests/vm/test_vmalloc.sh