On Tue, May 09, 2023 at 04:38:53PM +0200, Michal Privoznik wrote:
After previous cleanup, there's not a single caller that would call either qemuDomainGetMemLockLimitBytes() or qemuDomainAdjustMaxMemLock() with @forceVFIO set. All callers pass false.Drop the unneeded argument from both functions. Signed-off-by: Michal Privoznik <mpriv...@redhat.com>
Reviewed-by: Martin Kletzander <mklet...@redhat.com>
---
src/qemu/qemu_domain.c | 42 ++++++++++++++++-------------------------
src/qemu/qemu_domain.h | 6 ++----
src/qemu/qemu_hotplug.c | 16 ++++++++--------
src/qemu/qemu_process.c | 2 +-
tests/qemumemlocktest.c | 2 +-
5 files changed, 28 insertions(+), 40 deletions(-)
diff --git a/src/qemu/qemu_domain.c b/src/qemu/qemu_domain.c
index b5b4184782..fac611d920 100644
--- a/src/qemu/qemu_domain.c
+++ b/src/qemu/qemu_domain.c
@@ -9650,7 +9644,7 @@ qemuDomainGetMemLockLimitBytes(virDomainDef *def,
*/
int factor = nvdpa + nnvme;
- if (nvfio || forceVFIO) {
+ if (nvfio) {
if (nvfio && def->iommu)
You can drop the 'nvfio && ' part from here too.
signature.asc
Description: PGP signature
