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? Jason
