From: sashiko-bot@kernel.org
To: "Gregory Price" <gourry@gourry.net>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 4/5] selftests: KVM: guest_memfd: let the gmem_test() harness bind a node
Date: Wed, 02 Sep 2026 19:59:59 +0000 [thread overview]
Message-ID: <20260902195959.B5C771F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260902194657.79075-5-gourry@gourry.net>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Build failure due to missing tools UAPI header sync for GUEST_MEMFD_FLAG_BIND_NODE.
--
commit 93b29e02dbc130205238f8312d9571e48df529a8
Author: Gregory Price <gourry@gourry.net>
Subject: selftests: KVM: guest_memfd: let the gmem_test() harness bind a node
This commit extends create_guest_memfd() to accept a node argument in order
to test the GUEST_MEMFD_FLAG_BIND_NODE functionality. It ignores the node
argument if the BIND_NODE flag is not provided.
> diff --git a/tools/testing/selftests/kvm/guest_memfd_test.c b/tools/testing/selftests/kvm/guest_memfd_test.c
> index 2233d871a38f4..1818e0fea5690 100644
> --- a/tools/testing/selftests/kvm/guest_memfd_test.c
> +++ b/tools/testing/selftests/kvm/guest_memfd_test.c
> @@ -25,6 +25,31 @@
>
> static size_t page_size;
>
> +static int __create_guest_memfd_node(struct kvm_vm *vm, u64 size, u64 flags,
> + u32 node, u32 pad)
> +{
> + struct kvm_create_guest_memfd guest_memfd = {
> + .size = size,
> + .flags = flags,
> + .node = node,
> + .pad = pad,
> + };
[Severity: Low]
Does this cause a build failure when compiling the KVM selftests?
This patch updates the tests to use the new .node and .pad fields in
struct kvm_create_guest_memfd here, as well as the
GUEST_MEMFD_FLAG_BIND_NODE macro further down.
However, the tools/include/uapi/linux/kvm.h header doesn't seem to be
synchronized in this patch. Because the selftests Makefile prioritizes
the tools/include path over system headers, won't the compiler fail with
undeclared identifier errors when it processes these new fields and macros?
Should tools/include/uapi/linux/kvm.h be updated either in this patch or
in a prerequisite commit to prevent breaking the local build?
> +
> + return __vm_ioctl(vm, KVM_CREATE_GUEST_MEMFD, &guest_memfd);
> +}
> +
> +static int create_guest_memfd(struct kvm_vm *vm, u64 size, u64 flags, u32 node)
> +{
> + int fd;
> +
> + if (!(flags & GUEST_MEMFD_FLAG_BIND_NODE))
> + return vm_create_guest_memfd(vm, size, flags);
> +
> + fd = __create_guest_memfd_node(vm, size, flags, node, 0);
> + TEST_ASSERT(fd >= 0, KVM_IOCTL_ERROR(KVM_CREATE_GUEST_MEMFD, fd));
> + return fd;
> +}
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260902194657.79075-1-gourry@gourry.net?part=4
next prev parent reply other threads:[~2026-09-02 20:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 19:46 [PATCH 0/5] KVM: guest_memfd: bind backing memory to a NUMA node Gregory Price
2026-09-02 19:46 ` [PATCH 1/5] mm/mempolicy: add mempolicy_create() Gregory Price
2026-09-02 19:46 ` [PATCH 2/5] mm/mempolicy: add mpol_set_shared_policy_range() Gregory Price
2026-09-02 19:46 ` [PATCH 3/5] KVM: guest_memfd: bind backing memory to a NUMA node at creation Gregory Price
2026-09-02 20:00 ` sashiko-bot
2026-09-02 19:46 ` [PATCH 4/5] selftests: KVM: guest_memfd: let the gmem_test() harness bind a node Gregory Price
2026-09-02 19:59 ` sashiko-bot [this message]
2026-09-02 19:46 ` [PATCH 5/5] selftests: KVM: guest_memfd: test GUEST_MEMFD_FLAG_BIND_NODE Gregory Price
2026-09-02 20:04 ` sashiko-bot
2026-09-09 22:41 ` [PATCH 0/5] KVM: guest_memfd: bind backing memory to a NUMA node Ackerley Tng
2026-09-09 23:10 ` Gregory Price
2026-09-09 23:23 ` Ackerley Tng
2026-09-09 23:41 ` Gregory Price
2026-09-10 11:32 ` David Hildenbrand (Arm)
2026-09-10 13:39 ` Gregory Price
2026-09-10 14:00 ` David Hildenbrand (Arm)
2026-09-10 11:30 ` David Hildenbrand (Arm)
2026-09-10 13:40 ` Gregory Price
2026-09-10 14:05 ` David Hildenbrand (Arm)
2026-09-10 14:46 ` 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=20260902195959.B5C771F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=gourry@gourry.net \
--cc=kvm@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.