xiaomi-sm8450/android_kernel_xiaomi_sm8450
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

KVM: Documentation: Minor fixups

Browse Source 
In preparation for documenting a new capability let's fix up the
formatting of the current ones.

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-6-drjones@redhat.com
This commit is contained in:
Andrew Jones
2020-08-04 19:06:03 +02:00
committed by Marc Zyngier
parent 53f985584e
commit 739c7af7da
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
Documentation/virt/kvm/api.rst
View File

@@ -6130,7 +6130,7 @@ HvCallSendSyntheticClusterIpi, HvCallSendSyntheticClusterIpiEx.
8.21 KVM_CAP_HYPERV_DIRECT_TLBFLUSH 8.21 KVM_CAP_HYPERV_DIRECT_TLBFLUSH
----------------------------------- -----------------------------------
:Architecture: x86 :Architectures: x86
This capability indicates that KVM running on top of Hyper-V hypervisor This capability indicates that KVM running on top of Hyper-V hypervisor
enables Direct TLB flush for its guests meaning that TLB flush enables Direct TLB flush for its guests meaning that TLB flush
@@ -6143,16 +6143,17 @@ in CPUID and only exposes Hyper-V identification. In this case, guest
thinks it's running on Hyper-V and only use Hyper-V hypercalls. thinks it's running on Hyper-V and only use Hyper-V hypercalls.
8.22 KVM_CAP_S390_VCPU_RESETS 8.22 KVM_CAP_S390_VCPU_RESETS
-----------------------------
Architectures: s390 :Architectures: s390
This capability indicates that the KVM_S390_NORMAL_RESET and This capability indicates that the KVM_S390_NORMAL_RESET and
KVM_S390_CLEAR_RESET ioctls are available. KVM_S390_CLEAR_RESET ioctls are available.
8.23 KVM_CAP_S390_PROTECTED 8.23 KVM_CAP_S390_PROTECTED
---------------------------
Architecture: s390 :Architectures: s390
This capability indicates that the Ultravisor has been initialized and This capability indicates that the Ultravisor has been initialized and
KVM can therefore start protected VMs. KVM can therefore start protected VMs.