From: Sean Christopherson <seanjc@google.com>
To: Ackerley Tng <ackerleytng@google.com>
Cc: kartikey406@gmail.com, pbonzini@redhat.com, shuah@kernel.org,
kvm@vger.kernel.org, linux-kselftest@vger.kernel.org,
vannapurve@google.com, Liam.Howlett@oracle.com,
akpm@linux-foundation.org, baohua@kernel.org,
baolin.wang@linux.alibaba.com, david@kernel.org,
dev.jain@arm.com, i@maskray.me, lance.yang@linux.dev,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
lorenzo.stoakes@oracle.com, npache@redhat.com,
ryan.roberts@arm.com, shy828301@gmail.com,
stable@vger.kernel.org,
syzbot+33a04338019ac7e43a44@syzkaller.appspotmail.com,
ziy@nvidia.com
Subject: Re: [PATCH] KVM: selftests: Test MADV_COLLAPSE on GUEST_MEMFD
Date: Tue, 17 Feb 2026 07:15:27 -0800 [thread overview]
Message-ID: <aZSGD-EGSR3Z5Qyi@google.com> (raw)
In-Reply-To: <20260217014402.2554832-1-ackerleytng@google.com>
On Tue, Feb 17, 2026, Ackerley Tng wrote:
> diff --git a/tools/testing/selftests/kvm/guest_memfd_test.c b/tools/testing/selftests/kvm/guest_memfd_test.c
> index 618c937f3c90f..d16341a4a315d 100644
> --- a/tools/testing/selftests/kvm/guest_memfd_test.c
> +++ b/tools/testing/selftests/kvm/guest_memfd_test.c
> @@ -171,6 +171,77 @@ static void test_numa_allocation(int fd, size_t total_size)
> kvm_munmap(mem, total_size);
> }
>
> +static size_t getpmdsize(void)
This absolutely belongs in library/utility code.
> +{
> + const char *path = "/sys/kernel/mm/transparent_hugepage/hpage_pmd_size";
> + static size_t pmd_size = -1;
> + FILE *fp;
> +
> + if (pmd_size != -1)
> + return pmd_size;
> +
> + fp = fopen(path, "r");
> + TEST_ASSERT(fp, "Couldn't open %s to read PMD size.", path);
This will likely assert on a kernel without THP support.
> + TEST_ASSERT_EQ(fscanf(fp, "%lu", &pmd_size), 1);
> +
> + TEST_ASSERT_EQ(fclose(fp), 0);
Please try to extend tools/testing/selftests/kvm/include/kvm_syscalls.h.
> +
> + return pmd_size;
> +}
> +
> +static void test_collapse(struct kvm_vm *vm, uint64_t flags)
> +{
> + const size_t pmd_size = getpmdsize();
> + char *mem;
> + off_t i;
> + int fd;
> +
> + fd = vm_create_guest_memfd(vm, pmd_size * 2,
> + GUEST_MEMFD_FLAG_MMAP |
> + GUEST_MEMFD_FLAG_INIT_SHARED);
> +
> + /*
> + * Use aligned address so that MADV_COLLAPSE will not be
> + * filtered out early in the collapsing routine.
Please elaborate, the value below is way more magical than just being aligned.
> + */
> +#define ALIGNED_ADDRESS ((void *)0x4000000000UL)
Use a "const void *" instead of #define inside a function. And use one of the
appropriate size macros, e.g.
const void *ALIGNED_ADDRESS = (void *)(SZ_1G * <some magic value>);
But why hardcode a virtual address in the first place? If you a specific
alignment, just allocate enough virtual memory to be able to meet those alignment
requirements.
> + mem = mmap(ALIGNED_ADDRESS, pmd_size, PROT_READ | PROT_WRITE,
> + MAP_FIXED | MAP_SHARED, fd, 0);
> + TEST_ASSERT_EQ(mem, ALIGNED_ADDRESS);
> +
> + /*
> + * Use reads to populate page table to avoid setting dirty
> + * flag on page.
> + */
> + for (i = 0; i < pmd_size; i += getpagesize())
> + READ_ONCE(mem[i]);
> +
> + /*
> + * Advising the use of huge pages in guest_memfd should be
> + * fine...
> + */
> + TEST_ASSERT_EQ(madvise(mem, pmd_size, MADV_HUGEPAGE), 0);
> +
> + /*
> + * ... but collapsing folios must not be supported to avoid
> + * mapping beyond shared ranges into host userspace page
> + * tables.
> + */
> + TEST_ASSERT_EQ(madvise(mem, pmd_size, MADV_COLLAPSE), -1);
> + TEST_ASSERT_EQ(errno, EINVAL);
> +
> + /*
> + * Removing from host page tables and re-faulting should be
> + * fine; should not end up faulting in a collapsed/huge folio.
> + */
> + TEST_ASSERT_EQ(madvise(mem, pmd_size, MADV_DONTNEED), 0);
> + READ_ONCE(mem[0]);
> +
> + kvm_munmap(mem, pmd_size);
> + kvm_close(fd);
> +}
> +
> static void test_fault_sigbus(int fd, size_t accessible_size, size_t map_size)
> {
> const char val = 0xaa;
> @@ -370,6 +441,7 @@ static void __test_guest_memfd(struct kvm_vm *vm, uint64_t flags)
> gmem_test(mmap_supported, vm, flags);
> gmem_test(fault_overflow, vm, flags);
> gmem_test(numa_allocation, vm, flags);
> + test_collapse(vm, flags);
Why diverge from everything else? Yeah, the size is different, but that's easy
enough to handle. And presumably the THP query needs to be able to fail gracefully,
so something like this?
diff --git a/tools/testing/selftests/kvm/guest_memfd_test.c b/tools/testing/selftests/kvm/guest_memfd_test.c
index 618c937f3c90..e942adae1f59 100644
--- a/tools/testing/selftests/kvm/guest_memfd_test.c
+++ b/tools/testing/selftests/kvm/guest_memfd_test.c
@@ -350,14 +350,28 @@ static void test_guest_memfd_flags(struct kvm_vm *vm)
}
}
-#define gmem_test(__test, __vm, __flags) \
+#define __gmem_test(__test, __vm, __flags, __size) \
do { \
- int fd = vm_create_guest_memfd(__vm, page_size * 4, __flags); \
+ int fd = vm_create_guest_memfd(__vm, __size, __flags); \
\
- test_##__test(fd, page_size * 4); \
+ test_##__test(fd, __size); \
close(fd); \
} while (0)
+#define gmem_test(__test, __vm, __flags) \
+ __gmem_test(__test, __vm, __flags, page_size * 4)
+
+#define gmem_test_huge_pmd(__test, __vm, __flags) \
+do { \
+ size_t pmd_size = kvm_get_thp_pmd_size(); \
+ \
+ if (!pmd_size) \
+ break; \
+ \
+ __gmem_test(__test, __vm, __flags, pmd_size * 2); \
+} while (0)
+
+
static void __test_guest_memfd(struct kvm_vm *vm, uint64_t flags)
{
test_create_guest_memfd_multiple(vm);
next prev parent reply other threads:[~2026-02-17 15:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 0:15 [PATCH v2] mm: thp: deny THP for files on anonymous inodes Deepanshu Kartikey
2026-02-14 11:27 ` Lance Yang
2026-02-15 22:48 ` Ackerley Tng
2026-02-15 12:41 ` David Hildenbrand (Arm)
2026-02-15 20:29 ` Barry Song
2026-02-16 6:47 ` Ackerley Tng
2026-02-16 15:01 ` Lorenzo Stoakes
2026-02-17 1:44 ` [PATCH] KVM: selftests: Test MADV_COLLAPSE on GUEST_MEMFD Ackerley Tng
2026-02-17 15:15 ` Sean Christopherson [this message]
2026-02-20 23:59 ` Ackerley Tng
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=aZSGD-EGSR3Z5Qyi@google.com \
--to=seanjc@google.com \
--cc=Liam.Howlett@oracle.com \
--cc=ackerleytng@google.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=i@maskray.me \
--cc=kartikey406@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=npache@redhat.com \
--cc=pbonzini@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=shy828301@gmail.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+33a04338019ac7e43a44@syzkaller.appspotmail.com \
--cc=vannapurve@google.com \
--cc=ziy@nvidia.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