On Fri, Mar 24, 2017 at 02:01:34PM -0400, Luiz Capitulino wrote:
On Thu, 23 Mar 2017 19:16:39 +0100
Andrea Bolognani <abologna(a)redhat.com> wrote:
> A problem reported recently to the mailing list[1] uncovered
> some flaws in the way we deal with setting the memory locking
> limit for QEMU guests.
>
> This series solves those issues and adds test suite coverage
> to hopefully prevent more bugs from popping up in the future.
Tested-by: Luiz Capitulino <lcapitulino(a)redhat.com>
>
>
> [1]
https://www.redhat.com/archives/libvir-list/2017-March/msg00534.html
>
> Andrea Bolognani (8):
> Revert "qemu: Forbid <memoryBacking><locked> without
> <memtune><hard_limit>"
> qemu: Remove qemuDomainRequiresMemLock()
> qemu: Fix memory locking limit calculation
> process: Translate "unlimited" correctly
> command: Introduce virCommandGetMaxMemLock()
> tests: Introduce virTestCompareToULL()
ACK to these first 6. I have to at least mention that I don't like the
fact that we need the sixth one, but we do and that's how the compare
functions work =)
> tests: Introduce QEMU memory locking limit tests
> docs: Improve documentation related to memory locking
>