[libvirt] [PATCH 5/6] qemu: Reduce memlock limit after detaching hostdev

Andrea Bolognani abologna at redhat.com
Tue Nov 24 13:56:37 UTC 2015


We increase the limit before plugging in a PCI hostdev or a memory
module because some memory might need to be locked due to eg. VFIO.

Of course we should do the opposite after unplugging a device: this
was already the case for memory modules, but not for hostdevs.
---
 src/qemu/qemu_hotplug.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/src/qemu/qemu_hotplug.c b/src/qemu/qemu_hotplug.c
index a5c134a..04baeff 100644
--- a/src/qemu/qemu_hotplug.c
+++ b/src/qemu/qemu_hotplug.c
@@ -3070,6 +3070,12 @@ qemuDomainRemoveHostDevice(virQEMUDriverPtr driver,
         networkReleaseActualDevice(vm->def, net);
         virDomainNetDefFree(net);
     }
+
+    /* QEMU might no longer need to lock as much memory, eg. we just detached
+     * a VFIO device, so adjust the limit here */
+    if (qemuDomainAdjustMaxMemLock(vm) < 0)
+        VIR_WARN("Failed to adjust locked memory limit");
+
     ret = 0;
 
  cleanup:
-- 
2.5.0




More information about the libvir-list mailing list