Re: [PATCH 4/5] KVM: Documentation minor fixups

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2020-07-11 11:04, Andrew Jones wrote:
Reviewed-by: Steven Price <steven.price@xxxxxxx>
Signed-off-by: Andrew Jones <drjones@xxxxxxxxxx>

It'd be good to have an actual commit message.

---
 Documentation/virt/kvm/api.rst | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
index 320788f81a05..3bd96c1a3962 100644
--- a/Documentation/virt/kvm/api.rst
+++ b/Documentation/virt/kvm/api.rst
@@ -6122,7 +6122,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
@@ -6135,16 +6135,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.

But this seems to be an otherwise unrelated patch.
I'm happy to take it, but it seems odd here.

Thanks,

        M.
--
Jazz is not dead. It just smells funny...



[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux