[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [PATCH for-4.15] x86/mem_sharing: copy parent VM's hostp2m's max_mapped_pfn during forking
Tamas K Lengyel writes ("Re: [PATCH for-4.15] x86/mem_sharing: copy parent VM's hostp2m's max_mapped_pfn during forking"): > On Thu, Mar 18, 2021 at 5:36 PM Tamas K Lengyel <tamas.lengyel@xxxxxxxxx> > wrote: > > > > When creating a VM fork copy the parent VM's hostp2m max_mapped_pfn value. > > Some > > toolstack relies on the XENMEM_maximum_gpfn value to establish the maximum > > addressable physical memory in the VM and for forks that have not yet been > > unpaused that value is not going to reflect the correct max gpfn that's > > possible to populate into the p2m. This patch fixes the issue. ... > CC-ing Ian as 4.15 release manager. This patch is safe to include in > 4.15 as it's a minor fix in a tech preview feature that's not even > compiled by default. As far as I can tell this patch is lacking a maintainer review ? Release-Acked-by: Ian Jackson <iwj@xxxxxxxxxxxxxx> *Provided that it is committed today* I'm not sure how likely that is. Thanks, Ian.
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |