Commit 739c7af7 authored by Andrew Jones's avatar Andrew Jones Committed by Marc Zyngier
Browse files

KVM: Documentation: Minor fixups 



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

Signed-off-by: default avatarAndrew Jones <drjones@redhat.com>
Signed-off-by: default avatarMarc Zyngier <maz@kernel.org>
Reviewed-by: default avatarSteven Price <steven.price@arm.com>
Link: https://lore.kernel.org/r/20200804170604.42662-6-drjones@redhat.com
parent 53f98558

Documentation/virt/kvm/api.rst

+5 −4
Original line number Diff line number Diff line
@@ -6130,7 +6130,7 @@ HvCallSendSyntheticClusterIpi, HvCallSendSyntheticClusterIpiEx. 
8.21 KVM_CAP_HYPERV_DIRECT_TLBFLUSH

-----------------------------------



:Architecture: x86

:Architectures: x86



This capability indicates that KVM running on top of Hyper-V hypervisor

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.



8.22 KVM_CAP_S390_VCPU_RESETS

-----------------------------



Architectures: s390

:Architectures: s390



This capability indicates that the KVM_S390_NORMAL_RESET and

KVM_S390_CLEAR_RESET ioctls are available.



8.23 KVM_CAP_S390_PROTECTED

---------------------------



Architecture: s390



:Architectures: s390



This capability indicates that the Ultravisor has been initialized and

KVM can therefore start protected VMs.

CRA Git | Maintained and supported by SUSTech CRA and CCSE