Re: [Xen-devel] [PATCH v2] x86/shadow: adjust minimum allocation calculations

2019-02-09 Thread Tim Deegan
At 04:41 -0700 on 07 Feb (1549514492), Jan Beulich wrote: > A previously bad situation has become worse with the early setting of > ->max_vcpus: The value returned by shadow_min_acceptable_pages() has > further grown, and hence now holds back even more memory from use for > the p2m. > > Make

Re: [Xen-devel] [PATCH v2] x86/shadow: adjust minimum allocation calculations

2019-02-08 Thread George Dunlap
On Thu, Feb 7, 2019 at 11:42 AM Jan Beulich wrote: > > A previously bad situation has become worse with the early setting of > ->max_vcpus: The value returned by shadow_min_acceptable_pages() has > further grown, and hence now holds back even more memory from use for > the p2m. > > Make

Re: [Xen-devel] [PATCH v2] x86/shadow: adjust minimum allocation calculations

2019-02-07 Thread Juergen Gross
On 07/02/2019 12:41, Jan Beulich wrote: > A previously bad situation has become worse with the early setting of > ->max_vcpus: The value returned by shadow_min_acceptable_pages() has > further grown, and hence now holds back even more memory from use for > the p2m. > > Make sh_min_allocation()

[Xen-devel] [PATCH v2] x86/shadow: adjust minimum allocation calculations

2019-02-07 Thread Jan Beulich
A previously bad situation has become worse with the early setting of ->max_vcpus: The value returned by shadow_min_acceptable_pages() has further grown, and hence now holds back even more memory from use for the p2m. Make sh_min_allocation() account for all p2m memory needed for shadow_enable()