linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: mike.kravetz@oracle.com, muchun.song@linux.dev,
	akpm@linux-foundation.org
Cc: linux-mm@kvack.org, riel@surriel.com
Subject: [PATCH v2 0/2] New selftest for mm
Date: Thu,  5 Oct 2023 09:39:20 -0700	[thread overview]
Message-ID: <20231005163922.87568-1-leitao@debian.org> (raw)

This is a simple test case that reproduces an mm problem[1], where a page
fault races with madvise(), and it is not trivial to reproduce and
debug.

This test-case aims to avoid such race problems from happening again,
impacting workloads that leverages external allocators, such as
tcmalloc, jemalloc, etc.

Changelog:
---------

V2:
 * Remove some unnecessary checks
 * Skip the test instead of failing in some cases

[1] https://lore.kernel.org/all/20231001005659.2185316-1-riel@surriel.com/#r

Breno Leitao (2):
  selftests/mm: export get_free_hugepages()
  selftests/mm: Add a new test for madv and hugetlb

 tools/testing/selftests/mm/Makefile           |  1 +
 tools/testing/selftests/mm/hugetlb-madvise.c  | 19 -----
 .../selftests/mm/hugetlb_fault_after_madv.c   | 73 +++++++++++++++++++
 tools/testing/selftests/mm/run_vmtests.sh     |  4 +
 tools/testing/selftests/mm/vm_util.c          | 19 +++++
 tools/testing/selftests/mm/vm_util.h          |  1 +
 6 files changed, 98 insertions(+), 19 deletions(-)
 create mode 100644 tools/testing/selftests/mm/hugetlb_fault_after_madv.c

-- 
2.34.1



             reply	other threads:[~2023-10-05 16:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05 16:39 Breno Leitao [this message]
2023-10-05 16:39 ` [PATCH v2 1/2] selftests/mm: export get_free_hugepages() Breno Leitao
2023-10-06  3:54   ` Rik van Riel
2023-10-05 16:39 ` [PATCH v2 2/2] selftests/mm: Add a new test for madv and hugetlb Breno Leitao
2023-10-06  3:55   ` Rik van Riel
2023-11-02 12:24   ` Ryan Roberts
2023-11-02 12:29     ` Ryan Roberts
2023-11-03 13:59       ` Breno Leitao
2023-11-03 14:47         ` Ryan Roberts

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=20231005163922.87568-1-leitao@debian.org \
    --to=leitao@debian.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=mike.kravetz@oracle.com \
    --cc=muchun.song@linux.dev \
    --cc=riel@surriel.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