[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <03d1ffc5-2752-4c2b-a95f-e9f337bdab9b@amd.com>
Date: Thu, 13 Feb 2025 23:57:21 +0530
From: Shivank Garg <shivankg@....com>
To: David Hildenbrand <david@...hat.com>, akpm@...ux-foundation.org,
willy@...radead.org, pbonzini@...hat.com
Cc: linux-fsdevel@...r.kernel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
linux-coco@...ts.linux.dev, chao.gao@...el.com, seanjc@...gle.com,
ackerleytng@...gle.com, vbabka@...e.cz, bharata@....com, nikunj@....com,
michael.day@....com, Neeraj.Upadhyay@....com, thomas.lendacky@....com,
michael.roth@....com
Subject: Re: [RFC PATCH v4 2/3] mm/mempolicy: export memory policy symbols
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@...hat.com>
>
Thanks for the suggestion.
I'll add it.
Best Regards,
Shivank
Powered by blists - more mailing lists