From: Shivank Garg <shivankg@amd.com>
To: David Hildenbrand <david@redhat.com>,
akpm@linux-foundation.org, willy@infradead.org,
pbonzini@redhat.com
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
linux-coco@lists.linux.dev, chao.gao@intel.com,
seanjc@google.com, ackerleytng@google.com, vbabka@suse.cz,
bharata@amd.com, nikunj@amd.com, michael.day@amd.com,
Neeraj.Upadhyay@amd.com, thomas.lendacky@amd.com,
michael.roth@amd.com
Subject: Re: [RFC PATCH v4 2/3] mm/mempolicy: export memory policy symbols
Date: Thu, 13 Feb 2025 23:57:21 +0530 [thread overview]
Message-ID: <03d1ffc5-2752-4c2b-a95f-e9f337bdab9b@amd.com> (raw)
In-Reply-To: <9392618e-32de-4a86-9e1e-bcfeefe39181@redhat.com>
On 2/12/2025 3:53 PM, David Hildenbrand wrote:
> On 10.02.25 07:32, Shivank Garg wrote:
>> Export memory policy related symbols needed by the KVM guest-memfd to
>> implement NUMA policy support.
>>
>> These symbols are required to implement per-memory region NUMA policies
>> for guest memory, allowing VMMs to control guest memory placement across
>> NUMA nodes.
>
> Probably worth mentioning something like
>
> "guest_memfd wants to implement support for NUMA policies just like shmem already does using the shared policy infrastructure. As guest_memfd currently resides in KVM module code, we have to export the relevant symbols.
>
> In the future, guest_memfd might be moved to core-mm, at which point the symbols no longer would have to be exported. When/if that happens is still unclear."
>
> Acked-by: David Hildenbrand <david@redhat.com>
>
Thanks for the suggestion.
I'll add it.
Best Regards,
Shivank
next prev parent reply other threads:[~2025-02-13 18:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 6:32 [RFC PATCH v4 0/3] Add NUMA mempolicy support for KVM guest-memfd Shivank Garg
2025-02-10 6:32 ` [RFC PATCH v4 1/3] mm/filemap: add mempolicy support to the filemap layer Shivank Garg
2025-02-12 10:03 ` David Hildenbrand
2025-02-13 18:27 ` Shivank Garg
2025-02-17 19:52 ` David Hildenbrand
2025-02-10 6:32 ` [RFC PATCH v4 2/3] mm/mempolicy: export memory policy symbols Shivank Garg
2025-02-12 10:23 ` David Hildenbrand
2025-02-13 18:27 ` Shivank Garg [this message]
2025-02-17 11:52 ` Vlastimil Babka
2025-02-18 15:22 ` Sean Christopherson
2025-02-19 6:45 ` Shivank Garg
2025-02-10 6:32 ` [RFC PATCH v4 3/3] KVM: guest_memfd: Enforce NUMA mempolicy using shared policy Shivank Garg
2025-02-12 10:39 ` David Hildenbrand
2025-02-13 18:27 ` Shivank Garg
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=03d1ffc5-2752-4c2b-a95f-e9f337bdab9b@amd.com \
--to=shivankg@amd.com \
--cc=Neeraj.Upadhyay@amd.com \
--cc=ackerleytng@google.com \
--cc=akpm@linux-foundation.org \
--cc=bharata@amd.com \
--cc=chao.gao@intel.com \
--cc=david@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=michael.day@amd.com \
--cc=michael.roth@amd.com \
--cc=nikunj@amd.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=thomas.lendacky@amd.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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