[PATCH 3/3] qemu: Explain why mlock size is modified when def->mem.locked is enabled

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



---
 src/qemu/qemu_domain.c | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/src/qemu/qemu_domain.c b/src/qemu/qemu_domain.c
index 11cd39e..7f2783b 100644
--- a/src/qemu/qemu_domain.c
+++ b/src/qemu/qemu_domain.c
@@ -3673,6 +3673,11 @@ qemuDomainRequiresMlock(virDomainDefPtr def)
 {
     size_t i;

+    /* Note that we do assume that the locked memory limit needs to be
+     * automatically adjusted during memory hotplug as it would cause a
+     * regression in behavior. The behavior was caused by improperly reverting
+     * all functionality depending on qemuDomainMemoryLimit in commit 16bcb3b616
+     */
     if (def->mem.locked)
         return true;

-- 
2.6.2

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list



[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]