[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z7Slzs_4jZ2qkPAi@google.com>
Date: Tue, 18 Feb 2025 07:22:54 -0800
From: Sean Christopherson <seanjc@...gle.com>
To: Vlastimil Babka <vbabka@...e.cz>
Cc: Shivank Garg <shivankg@....com>, akpm@...ux-foundation.org, willy@...radead.org,
pbonzini@...hat.com, 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, ackerleytng@...gle.com, david@...hat.com, 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 Mon, Feb 17, 2025, Vlastimil Babka wrote:
> On 2/10/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.
> >
> > Signed-off-by: Shivank Garg <shivankg@....com>
>
> I think we should use EXPORT_SYMBOL_GPL() these days.
>
> Wasn't there also some way to limit the exports to KVM?
The infrastructure is still a WIP[1], though when that lands, I definitely plan
on tightening down the KVM-induced exports[2].
[1] https://lore.kernel.org/all/20241202145946.108093528@infradead.org
[2] https://lore.kernel.org/all/ZzJOoFFPjrzYzKir@google.com
Powered by blists - more mailing lists