| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <9392618e-32de-4a86-9e1e-bcfeefe39181@redhat.com> Date: Wed, 12 Feb 2025 11:23:39 +0100 From: David Hildenbrand <david@...hat.com> To: Shivank Garg <shivankg@....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 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> -- Cheers, David / dhildenb
Powered by blists - more mailing lists