docs: kvm: fix WARNINGs from api.rst
Subsystems (2)
PATCH 1/1 docs: kvm: fix WARNINGs from api.rst
Use the api number 134 for KVM_GET_XSAVE2, instead of 42, which has been used by KVM_GET_XSAVE.
Also, fix the WARNINGs of the underlines being too short.
--- Documentation/virt/kvm/api.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
Documentation/virt/kvm/api.rst +3 -3
@@ -5545,8 +5545,8 @@ the trailing ``'\0'``, is indicated by ``name_size`` in the header. The Stats Data block contains an array of 64-bit values in the same order as the descriptors in Descriptors block. -4.42 KVM_GET_XSAVE2 ------------------- +4.134 KVM_GET_XSAVE2 +-------------------- :Capability: KVM_CAP_XSAVE2 :Architectures: x86
@@ -7363,7 +7363,7 @@ trap and emulate MSRs that are outside of the scope of KVM as well as limit the attack surface on KVM's MSR emulation code. 8.28 KVM_CAP_ENFORCE_PV_FEATURE_CPUID ------------------------------ +------------------------------------- Architectures: x86
Signature · 1 line
2.25.1
Hi Wei,
Quoted 6 lines · On Wed, 19 Jan 2022 23:50:03 -0500 Wei Wang <[email protected]> wrote:
Use the api number 134 for
KVM_GET_XSAVE2, instead of 42, which has been used byKVM_GET_XSAVE.
Also, fix the WARNINGs of the underlines being too short.Reported-by Stephen Rothwell <[email protected]>
Quoted 21 lines
Signed-off-by Wei Wang <[email protected]>--- Documentation/virt/kvm/api.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)Documentation/virt/kvm/api.rst +2
-2@@ -5545,8 +5545,8 @@ the trailing ``'\0'``, is indicated by ``name_size`` in the header. The Stats Data block contains an array of 64-bit values in the same order as the descriptors in Descriptors block. -4.42 KVM_GET_XSAVE2 ------------------- +4.134 KVM_GET_XSAVE2 +-------------------- :Capability: KVM_CAP_XSAVE2 :Architectures: x86
Documentation/virt/kvm/api.rst trap and emulate MSRs that are outside of the scope of KVM as well as · line 7369
Quoted 8 lines
Documentation/virt/kvm/api.rst +1
-1@@ -7363,7 +7363,7 @@ trap and emulate MSRs that are outside of the scope of KVM as well as limit the attack surface on KVM's MSR emulation code. 8.28 KVM_CAP_ENFORCE_PV_FEATURE_CPUID ------------------------------ +------------------------------------- Architectures: x86
Thanks.
Signature · 2 lines
Cheers, Stephen Rothwell
Quoted 26 lines · Wei Wang
Use the api number 134 for
KVM_GET_XSAVE2, instead of 42, which has been used byKVM_GET_XSAVE.
Also, fix the WARNINGs of the underlines being too short.Reported-by Stephen Rothwell <[email protected]>Signed-off-by Wei Wang <[email protected]>--- Documentation/virt/kvm/api.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)Documentation/virt/kvm/api.rst +2
-2@@ -5545,8 +5545,8 @@ the trailing ``'\0'``, is indicated by ``name_size`` in the header. The Stats Data block contains an array of 64-bit values in the same order as the descriptors in Descriptors block. -4.42 KVM_GET_XSAVE2 ------------------- +4.134 KVM_GET_XSAVE2 +-------------------- :Capability: KVM_CAP_XSAVE2 :Architectures: x86
Documentation/virt/kvm/api.rst trap and emulate MSRs that are outside of the scope of KVM as well as · line 7369
Quoted 8 lines
Documentation/virt/kvm/api.rst +1
-1@@ -7363,7 +7363,7 @@ trap and emulate MSRs that are outside of the scope of KVM as well as limit the attack surface on KVM's MSR emulation code. 8.28 KVM_CAP_ENFORCE_PV_FEATURE_CPUID ------------------------------ +------------------------------------- Architectures: x86
Queued, thanks.
Paolo