diff options
author | Andrew Jones <drjones@redhat.com> | 2020-08-04 19:06:04 +0200 |
---|---|---|
committer | Marc Zyngier <maz@kernel.org> | 2020-08-21 14:05:19 +0100 |
commit | 004a01241c5a0d375266ebf1c72f208de99294e9 (patch) | |
tree | 956e8aee5d5a69cbbdf3d5dff427bae747a003b1 /arch/x86/kvm | |
parent | 739c7af7daeede8e2ec78392f2617c965ce0342a (diff) | |
download | linux-stable-004a01241c5a0d375266ebf1c72f208de99294e9.tar.gz linux-stable-004a01241c5a0d375266ebf1c72f208de99294e9.tar.bz2 linux-stable-004a01241c5a0d375266ebf1c72f208de99294e9.zip |
arm64/x86: KVM: Introduce steal-time cap
arm64 requires a vcpu fd (KVM_HAS_DEVICE_ATTR vcpu ioctl) to probe
support for steal-time. However this is unnecessary, as only a KVM
fd is required, and it complicates userspace (userspace may prefer
delaying vcpu creation until after feature probing). Introduce a cap
that can be checked instead. While x86 can already probe steal-time
support with a kvm fd (KVM_GET_SUPPORTED_CPUID), we add the cap there
too for consistency.
Signed-off-by: Andrew Jones <drjones@redhat.com>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Reviewed-by: Steven Price <steven.price@arm.com>
Link: https://lore.kernel.org/r/20200804170604.42662-7-drjones@redhat.com
Diffstat (limited to 'arch/x86/kvm')
-rw-r--r-- | arch/x86/kvm/x86.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c index 599d73206299..c44d3a73b8eb 100644 --- a/arch/x86/kvm/x86.c +++ b/arch/x86/kvm/x86.c @@ -3581,6 +3581,9 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext) case KVM_CAP_SMALLER_MAXPHYADDR: r = (int) allow_smaller_maxphyaddr; break; + case KVM_CAP_STEAL_TIME: + r = sched_info_on(); + break; default: break; } |