]> git.ipfire.org Git - thirdparty/linux.git/commitdiff
KVM: Fix VM exit code for full dirty ring in API documentation
authorLeonardo Bras <leo.bras@arm.com>
Tue, 14 Oct 2025 15:28:02 +0000 (16:28 +0100)
committerSean Christopherson <seanjc@google.com>
Tue, 14 Oct 2025 22:19:05 +0000 (15:19 -0700)
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>
Documentation/virt/kvm/api.rst

index 6ae24c5ca5598f0e302f5de569217afa15528108..3382adefc772311e9836be892f88c2a8f34c9c7a 100644 (file)
@@ -8510,7 +8510,7 @@ Therefore, the ioctl must be called *before* reading the content of
 the dirty pages.
 
 The dirty ring can get full.  When it happens, the KVM_RUN of the
-vcpu will return with exit reason KVM_EXIT_DIRTY_LOG_FULL.
+vcpu will return with exit reason KVM_EXIT_DIRTY_RING_FULL.
 
 The dirty ring interface has a major difference comparing to the
 KVM_GET_DIRTY_LOG interface in that, when reading the dirty ring from