Re: [libvirt] [PATCH v2 1/3] qemu_domain: simplify non-VFIO memLockLimit calc for PPC64

2019-03-04 Thread Erik Skultety
On Mon, Mar 04, 2019 at 11:49:54AM -0300, Daniel Henrique Barboza wrote: > > > On 3/4/19 10:10 AM, Erik Skultety wrote: > > On Sun, Mar 03, 2019 at 10:23:12AM -0300, Daniel Henrique Barboza wrote: > > > passthroughLimit is being calculated even if usesVFIO is false. > > > After that, a if/else cond

Re: [libvirt] [PATCH v2 1/3] qemu_domain: simplify non-VFIO memLockLimit calc for PPC64

2019-03-04 Thread Daniel Henrique Barboza
On 3/4/19 10:10 AM, Erik Skultety wrote: On Sun, Mar 03, 2019 at 10:23:12AM -0300, Daniel Henrique Barboza wrote: passthroughLimit is being calculated even if usesVFIO is false. After that, a if/else conditional is used to check if we're going to sum it up with baseLimit. This patch initializ

Re: [libvirt] [PATCH v2 1/3] qemu_domain: simplify non-VFIO memLockLimit calc for PPC64

2019-03-04 Thread Erik Skultety
On Sun, Mar 03, 2019 at 10:23:12AM -0300, Daniel Henrique Barboza wrote: > passthroughLimit is being calculated even if usesVFIO is false. > After that, a if/else conditional is used to check if we're going > to sum it up with baseLimit. > > This patch initializes passthroughLimit to zero and alway

[libvirt] [PATCH v2 1/3] qemu_domain: simplify non-VFIO memLockLimit calc for PPC64

2019-03-03 Thread Daniel Henrique Barboza
passthroughLimit is being calculated even if usesVFIO is false. After that, a if/else conditional is used to check if we're going to sum it up with baseLimit. This patch initializes passthroughLimit to zero and always return memKB = baseLimit + passthroughLimit. The conditional is then used to cal