[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240802205003.353672-1-seanjc@google.com>
Date: Fri, 2 Aug 2024 13:49:57 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Sean Christopherson <seanjc@...gle.com>, Paolo Bonzini <pbonzini@...hat.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH 0/6] KVM: kvm_set_memory_region() cleanups
Cleanups related to kvm_set_memory_region(), salvaged from similar patches
that were flying around when we were sorting out KVM_SET_USER_MEMORY_REGION2.
I'm honestly 50/50 on whether this is all worthwhile, but in the end, I
decided I like having kvm_set_internal_memslot(). I think.
Sean Christopherson (6):
KVM: Open code kvm_set_memory_region() into its sole caller (ioctl()
API)
KVM: Assert slots_lock is held in __kvm_set_memory_region()
KVM: Add a dedicated API for setting KVM-internal memslots
KVM: x86: Drop double-underscores from __kvm_set_memory_region()
KVM: Disallow all flags for KVM-internal memslots
KVM: Move flags check for user memory regions to the ioctl() specific
API
arch/x86/kvm/x86.c | 4 +-
include/linux/kvm_host.h | 8 ++--
virt/kvm/kvm_main.c | 87 +++++++++++++++++-----------------------
3 files changed, 41 insertions(+), 58 deletions(-)
base-commit: 332d2c1d713e232e163386c35a3ba0c1b90df83f
--
2.46.0.rc2.264.g509ed76dc8-goog
Powered by blists - more mailing lists