On Tue, Sep 16, 2025 at 10:05:16AM -0300, Jason Gunthorpe wrote: > On Mon, Sep 15, 2025 at 07:36:25PM +0300, Mike Rapoport wrote: > > > Under the covers it all uses the generic folio based code we already > > > have, but we should have appropriate wrappers around that code that > > > make clear these patterns. > > > > Right, but that does not mean that vmalloc preserve/restore should use the > > public KHO APIs and avoid using internal methods. > > I think it does, the same way vmalloc is layered on top of the buddy > allocator. Why wouldn't you build things in clean understandable > layers like this?
Here it's more like __vmalloc_node_range_noprof() and get_vm_area() calling __get_vm_area() > Jason -- Sincerely yours, Mike.
