Re: [Xen-devel] [PATCH 2/2] xen: enable BALLOON_MEMORY_HOTPLUG by default

2020-03-26 Thread Ian Jackson
Roger Pau Monne writes ("Re: [PATCH 2/2] xen: enable BALLOON_MEMORY_HOTPLUG by default"): > I would rather have it always on if possible, as gntdev or privcmd > (when used to map foreign pages from user-space) will also require it, > and they are not gated on XEN_BACKEND AFAICT. Currently there

Re: [Xen-devel] [PATCH 2/2] xen: enable BALLOON_MEMORY_HOTPLUG by default

2020-03-24 Thread Roger Pau Monné
On Tue, Mar 24, 2020 at 04:09:35PM +0100, Jürgen Groß wrote: > On 24.03.20 16:00, Roger Pau Monne wrote: > > Without it a PVH dom0 is mostly useless, as it would balloon down huge > > amounts of RAM in order get physical address space to map foreign > > memory and grants, ultimately leading to an

Re: [Xen-devel] [PATCH 2/2] xen: enable BALLOON_MEMORY_HOTPLUG by default

2020-03-24 Thread Jürgen Groß
On 24.03.20 16:00, Roger Pau Monne wrote: Without it a PVH dom0 is mostly useless, as it would balloon down huge amounts of RAM in order get physical address space to map foreign memory and grants, ultimately leading to an out of memory situation. Such option is also needed for HVM or PVH

[Xen-devel] [PATCH 2/2] xen: enable BALLOON_MEMORY_HOTPLUG by default

2020-03-24 Thread Roger Pau Monne
Without it a PVH dom0 is mostly useless, as it would balloon down huge amounts of RAM in order get physical address space to map foreign memory and grants, ultimately leading to an out of memory situation. Such option is also needed for HVM or PVH driver domains, since they also require mapping