Re: [PATCH v4] xen/balloon: add late_initcall_sync() for initial ballooning done

2021-11-05 Thread Boris Ostrovsky
On 11/2/21 5:19 AM, Juergen Gross wrote: When running as PVH or HVM guest with actual memory < max memory the hypervisor is using "populate on demand" in order to allow the guest to balloon down from its maximum memory size. For this to work correctly the guest must not touch more memory pages

Re: [PATCH v4] xen/balloon: add late_initcall_sync() for initial ballooning done

2021-11-04 Thread Boris Ostrovsky
And if so, would you mind doing this while committing (I have one day off tomorrow)? Yes, of course. Thanks. So I'll change this to pr_notice, even though it's not the best solution. -boris

Re: [PATCH v4] xen/balloon: add late_initcall_sync() for initial ballooning done

2021-11-04 Thread Juergen Gross
On 04.11.21 17:34, Boris Ostrovsky wrote: On 11/4/21 12:21 PM, Juergen Gross wrote: On 04.11.21 16:55, Boris Ostrovsky wrote: On 11/3/21 9:55 PM, Boris Ostrovsky wrote: On 11/2/21 5:19 AM, Juergen Gross wrote: When running as PVH or HVM guest with actual memory < max memory the hypervisor

Re: [PATCH v4] xen/balloon: add late_initcall_sync() for initial ballooning done

2021-11-04 Thread Boris Ostrovsky
On 11/4/21 12:21 PM, Juergen Gross wrote: On 04.11.21 16:55, Boris Ostrovsky wrote: On 11/3/21 9:55 PM, Boris Ostrovsky wrote: On 11/2/21 5:19 AM, Juergen Gross wrote: When running as PVH or HVM guest with actual memory < max memory the hypervisor is using "populate on demand" in order to

Re: [PATCH v4] xen/balloon: add late_initcall_sync() for initial ballooning done

2021-11-04 Thread Marek Marczykowski-Górecki
On Thu, Nov 04, 2021 at 11:55:34AM -0400, Boris Ostrovsky wrote: > This appears to have noticeable effect on boot time (and boot experience in > general). Yes, this is kind of intentional. It avoids killing the domain ("out of PoD memory") for the price of increased boot time. I still wonder why

Re: [PATCH v4] xen/balloon: add late_initcall_sync() for initial ballooning done

2021-11-04 Thread Juergen Gross
On 04.11.21 16:55, Boris Ostrovsky wrote: On 11/3/21 9:55 PM, Boris Ostrovsky wrote: On 11/2/21 5:19 AM, Juergen Gross wrote: When running as PVH or HVM guest with actual memory < max memory the hypervisor is using "populate on demand" in order to allow the guest to balloon down from its maxi

Re: [PATCH v4] xen/balloon: add late_initcall_sync() for initial ballooning done

2021-11-04 Thread Boris Ostrovsky
On 11/3/21 9:55 PM, Boris Ostrovsky wrote: On 11/2/21 5:19 AM, Juergen Gross wrote: When running as PVH or HVM guest with actual memory < max memory the hypervisor is using "populate on demand" in order to allow the guest to balloon down from its maximum memory size. For this to work correctl

Re: [PATCH v4] xen/balloon: add late_initcall_sync() for initial ballooning done

2021-11-03 Thread Boris Ostrovsky
On 11/2/21 5:19 AM, Juergen Gross wrote: When running as PVH or HVM guest with actual memory < max memory the hypervisor is using "populate on demand" in order to allow the guest to balloon down from its maximum memory size. For this to work correctly the guest must not touch more memory pages

[PATCH v4] xen/balloon: add late_initcall_sync() for initial ballooning done

2021-11-02 Thread Juergen Gross
When running as PVH or HVM guest with actual memory < max memory the hypervisor is using "populate on demand" in order to allow the guest to balloon down from its maximum memory size. For this to work correctly the guest must not touch more memory pages than its target memory size as otherwise the