Skip to content

Commit 04fd067

Browse files
Leonardo Brassean-jc
authored andcommitted
KVM: Fix VM exit code for full dirty ring in API documentation
While reading the documentation, I saw a exit code I could not grep for, to figure out it has a slightly different name. Fix that name in documentation so it points to the right exit code. Signed-off-by: Leonardo Bras <leo.bras@arm.com> Link: https://lore.kernel.org/r/20251014152802.13563-1-leo.bras@arm.com Signed-off-by: Sean Christopherson <seanjc@google.com>
1 parent 9259607 commit 04fd067

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

Documentation/virt/kvm/api.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8510,7 +8510,7 @@ Therefore, the ioctl must be called *before* reading the content of
85108510
the dirty pages.
85118511

85128512
The dirty ring can get full. When it happens, the KVM_RUN of the
8513-
vcpu will return with exit reason KVM_EXIT_DIRTY_LOG_FULL.
8513+
vcpu will return with exit reason KVM_EXIT_DIRTY_RING_FULL.
85148514

85158515
The dirty ring interface has a major difference comparing to the
85168516
KVM_GET_DIRTY_LOG interface in that, when reading the dirty ring from

0 commit comments

Comments
 (0)