diff options
author | Zeng Guang <guang.zeng@intel.com> | 2022-04-19 17:44:44 +0200 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2022-06-08 10:47:31 +0200 |
commit | 35875316384b71d23dc2a45a969732fc8cab16af (patch) | |
tree | 68c6884064bf6e7827c802d9b72aff9b966df290 /net/rxrpc/security.c | |
parent | KVM: Move kvm_arch_vcpu_precreate() under kvm->lock (diff) | |
download | linux-35875316384b71d23dc2a45a969732fc8cab16af.tar.xz linux-35875316384b71d23dc2a45a969732fc8cab16af.zip |
KVM: x86: Allow userspace to set maximum VCPU id for VM
Introduce new max_vcpu_ids in KVM for x86 architecture. Userspace
can assign maximum possible vcpu id for current VM session using
KVM_CAP_MAX_VCPU_ID of KVM_ENABLE_CAP ioctl().
This is done for x86 only because the sole use case is to guide
memory allocation for PID-pointer table, a structure needed to
enable VMX IPI.
By default, max_vcpu_ids set as KVM_MAX_VCPU_IDS.
Suggested-by: Sean Christopherson <seanjc@google.com>
Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
Signed-off-by: Zeng Guang <guang.zeng@intel.com>
Message-Id: <20220419154444.11888-1-guang.zeng@intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'net/rxrpc/security.c')
0 files changed, 0 insertions, 0 deletions