From: Sarthak Sharma <sarthak.sharma@arm.com>
To: "Gregory Price (Meta)" <gourry@gourry.net>,
linux-kselftest@vger.kernel.org, linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com,
akpm@linux-foundation.org, david@kernel.org, ljs@kernel.org,
liam@infradead.org, vbabka@kernel.org, rppt@kernel.org,
surenb@google.com, mhocko@suse.com, shuah@kernel.org
Subject: Re: [PATCH 3/8] selftests/mm: check MADV_COLD and MADV_PAGEOUT range handling
Date: Fri, 16 Oct 2026 17:47:57 +0530 [thread overview]
Message-ID: <73c55ce6-67a5-471d-811c-facf712b2fe9@arm.com> (raw)
In-Reply-To: <20261014175756.2035176-4-gourry@gourry.net>
Hi Gregory!
On 10/14/26 11:27 PM, Gregory Price (Meta) wrote:
> madvise(2) accepts a zero-length range, rejects an unaligned start, and
> reports an unmapped gap in the range with ENOMEM while still applying the
> advice to the mapped pages on either side.
>
> Check each of these for both hints. Around the gap, only MADV_PAGEOUT has
> an effect the test can observe, so only MADV_PAGEOUT is checked for
> paging out both neighbours, after a control page shows that swap works.
>
> Signed-off-by: Gregory Price (Meta) <gourry@gourry.net>
> ---
[...]
> +/*
> + * An unmapped gap in the range makes either hint fail with ENOMEM, after
> + * advising the mapped pages on both sides of the gap. Only MADV_PAGEOUT has
> + * an effect on those pages that the test can observe.
> + */
> +TEST_F(madvise, unmapped_gap_fails_after_advising)
> +{
> + char *mapping, *control;
> + bool swapped = false;
> + int retry;
> +
> + pin_to_current_cpu(_metadata);
> +
> + /* Make sure MADV_PAGEOUT can swap at all before relying on it. */
> + control = mmap(NULL, page_size, PROT_READ | PROT_WRITE,
> + MAP_PRIVATE | MAP_ANONYMOUS, -1, 0);
> + ASSERT_NE(control, MAP_FAILED);
> + control[0] = 1;
> + if (!pageout_until_swapped(_metadata, control, page_size,
> + self->pagemap_fd))
> + SKIP(return, "MADV_PAGEOUT did not swap the page");
This test is checking for both MADV_COLD and MADV_PAGEOUT. So if we skip
here because we couldn't pageout, then we don't test for MADV_COLD
behaviour at all. Do we want it this way, or should the tests for both
of these be separate?
> +
> + mapping = mmap(NULL, 3 * page_size, PROT_READ | PROT_WRITE,
> + MAP_PRIVATE | MAP_ANONYMOUS, -1, 0);
> + ASSERT_NE(mapping, MAP_FAILED);
> + mapping[0] = 1;
> + mapping[2 * page_size] = 1;
> + ASSERT_EQ(munmap(mapping + page_size, page_size), 0);
> +
> + ASSERT_EQ(madvise(mapping, 3 * page_size, MADV_COLD), -1);
> + ASSERT_EQ(errno, ENOMEM);
> + ASSERT_EQ(mapping[0], 1);
> + ASSERT_EQ(mapping[2 * page_size], 1);
> +
> + for (retry = 0; retry < PAGEOUT_RETRIES && !swapped; retry++) {
> + ASSERT_EQ(madvise(mapping, 3 * page_size, MADV_PAGEOUT), -1);
> + ASSERT_EQ(errno, ENOMEM);
> + swapped = pagemap_is_swapped(self->pagemap_fd, mapping) &&
> + pagemap_is_swapped(self->pagemap_fd,
> + mapping + 2 * page_size);
> + if (!swapped)
> + usleep(10000);
> + }
> + ASSERT_TRUE(swapped)
> + TH_LOG("MADV_PAGEOUT did not page out both sides of the gap");
> + ASSERT_EQ(mapping[0], 1);
> + ASSERT_EQ(mapping[2 * page_size], 1);
> +
> + ASSERT_EQ(munmap(mapping, page_size), 0);
> + ASSERT_EQ(munmap(mapping + 2 * page_size, page_size), 0);
> + ASSERT_EQ(munmap(control, page_size), 0);
> +}
> +
> /* Neither hint may fault a swapped page back in. */
> static void check_skips_swapped_pte(struct __test_metadata *_metadata,
> int pagemap_fd, int advice)
next prev parent reply other threads:[~2026-10-16 12:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 17:57 [PATCH 0/8] selftests/mm: add MADV_COLD and MADV_PAGEOUT contract tests Gregory Price (Meta)
2026-10-14 17:57 ` [PATCH 1/8] " Gregory Price (Meta)
2026-10-14 17:57 ` [PATCH 2/8] selftests/mm: check that MADV_PAGEOUT skips holes and swapped pages Gregory Price (Meta)
2026-10-14 17:57 ` [PATCH 3/8] selftests/mm: check MADV_COLD and MADV_PAGEOUT range handling Gregory Price (Meta)
2026-10-14 21:31 ` [PATCH] fixup! " Gregory Price (Meta)
2026-10-16 12:17 ` Sarthak Sharma [this message]
2026-10-16 13:22 ` [PATCH 3/8] " Gregory Price
2026-10-16 14:07 ` Gregory Price
2026-10-14 17:57 ` [PATCH 4/8] selftests/mm: check that MADV_COLD and MADV_PAGEOUT reject hugetlb Gregory Price (Meta)
2026-10-14 17:57 ` [PATCH 5/8] selftests/mm: check that MADV_COLD and MADV_PAGEOUT preserve shared memory Gregory Price (Meta)
2026-10-14 17:57 ` [PATCH 6/8] selftests/mm: check MADV_COLD and MADV_PAGEOUT on partly advised THPs Gregory Price (Meta)
2026-10-14 17:57 ` [PATCH 7/8] selftests/mm: check MADV_PAGEOUT file permissions Gregory Price (Meta)
2026-10-16 12:18 ` Sarthak Sharma
2026-10-16 13:48 ` Gregory Price
2026-10-14 17:57 ` [PATCH 8/8] selftests/mm: check that unauthorized MADV_PAGEOUT skips large file folios Gregory Price (Meta)
2026-10-14 21:26 ` Gregory Price
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=73c55ce6-67a5-471d-811c-facf712b2fe9@arm.com \
--to=sarthak.sharma@arm.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=gourry@gourry.net \
--cc=kernel-team@meta.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.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
all inboxes | Powered by JetHome®