On 09/27/23 at 09:13am, Stanislav Kinsburskii wrote: > On Wed, Sep 27, 2023 at 01:44:38PM +0800, Baoquan He wrote: > > Hi Stanislav, > > > > On 09/25/23 at 02:27pm, Stanislav Kinsburskii wrote: > > > This patch introduces a memory allocator specifically tailored for > > > persistent memory within the kernel. The allocator maintains > > > kernel-specific states like DMA passthrough device states, IOMMU state, and > > > more across kexec. > > > > Can you give more details about how this persistent memory pool will be > > utilized in a actual scenario? I mean, what problem have you met so that > > you have to introduce persistent memory pool to solve it? > > > > The major reason we have at the moment, is that Linux root partition > running on top of the Microsoft hypervisor needs to deposit pages to > hypervisor in runtime, when hypervisor runs out of memory. > "Depositing" here means, that Linux passes a set of its PFNs to the > hypervisor via hypercall, and hypervisor then uses these pages for its > own needs. > > Once deposited, these pages can't be accessed by Linux anymore and thus > must be preserved in "used" state across kexec, as hypervisor state is > unware of kexec. In the same time, these pages can we withdrawn when > usused. Thus, an allocator persistent across kexec looks reasonable for > this particular matter. Thanks for these details. The deposit and withdraw remind me the Balloon driver, David's virtio-mem, DLPAR on ppc which can hot increasing or shrinking phisical memory on guest OS. Can't microsoft hypervisor do the similar thing to reclaim or give back the memory from or to the 'Linux root partition' running on top of the hypervisor? Thanks Baoquan
