From: David Woodhouse <[email protected]> The KVM_CREATE_PLANE section was inserted between the .. _kvm_run: label and "5. The kvm_run structure", so the :ref:`kvm_run` in the KVM_CAP_SYNC_REGS text now links to KVM_CREATE_PLANE. It also took the number 4.145, which KVM_PPC_GET_COMPAT_CAPS already has, leaving 4.147 unused.
Move the label back above section 5 and number the section 4.147. Found by a local Sashiko review. Fixes the section placement in "Documentation: kvm: introduce "VM plane" concept". Fixes: https://lore.kernel.org/all/[email protected]/ Signed-off-by: David Woodhouse <[email protected]> --- Documentation/virt/kvm/api.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst index c1a6536354fd..9aa09d8a39dc 100644 --- a/Documentation/virt/kvm/api.rst +++ b/Documentation/virt/kvm/api.rst @@ -6821,11 +6821,9 @@ if the guest_memfd memory was pinned in IOMMU page tables. See also: :ref:`KVM_SET_MEMORY_ATTRIBUTES`. -.. _kvm_run: - .. _KVM_CREATE_PLANE: -4.145 KVM_CREATE_PLANE +4.147 KVM_CREATE_PLANE ---------------------- :Capability: KVM_CAP_PLANES @@ -6843,6 +6841,8 @@ in the future may use the plane id when planes are supported by hardware (as is the case for VMPLs in AMD), or if KVM supports accelerated plane switch operations (as might be the case for Hyper-V VTLs). +.. _kvm_run: + 5. The kvm_run structure ======================== -- 2.50.1
