On Fri, Nov 01, 2024 at 10:42:02AM -0300, Jason Gunthorpe wrote: > On Fri, Nov 01, 2024 at 01:01:00PM +0000, Gowans, James wrote: > > > Thanks Jason, that sounds perfect. I'll work on the next rev which will: > > - expose a filesystem which owns reserved/persistent memory, just like > > this patch. > > Is this step needed? > > If the guest memfd is already told to get 1G pages in some normal way, > why do we need a dedicated pool just for the KHO filesystem? > > Back to my suggestion, can't KHO simply freeze the guest memfd and > then extract the memory layout, and just use the normal allocator? > > Or do you have a hard requirement that only KHO allocated memory can > be preserved across kexec? KHO does not allocate memory, it gets the ranges to preserve, makes sure they are not overwritten during kexec and can be retrieved by the second kernel. For KHO it does not matter if the memory comes from a normal or a special allocator. > Jason -- Sincerely yours, Mike.
