Documentation: kvm: fix dirty log ioctl arch lists
Subsystems (2)
PATCH 1/1 Documentation: kvm: fix dirty log ioctl arch lists
KVM_GET_DIRTY_LOG is implemented by all architectures, not just x86, and KVM_CAP_MANUAL_DIRTY_LOG_PROTECT is additionally implemented by arm, arm64, and mips.
---
I skimmed all ioctls in the document to see if others needed to be fixed, but from my quick skim the only dirty ones seem to be the dirty log ones.
Documentation/virtual/kvm/api.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
Documentation/virtual/kvm/api.txt +3 -3
@@ -321,7 +321,7 @@ cpu's hardware control block. 4.8 KVM_GET_DIRTY_LOG (vm ioctl) Capability: basic -Architectures: x86 +Architectures: all Type: vm ioctl Parameters: struct kvm_dirty_log (in/out) Returns: 0 on success, -1 on error
@@ -3810,7 +3810,7 @@ to I/O ports. 4.117 KVM_CLEAR_DIRTY_LOG (vm ioctl) Capability: KVM_CAP_MANUAL_DIRTY_LOG_PROTECT -Architectures: x86 +Architectures: x86, arm, arm64, mips Type: vm ioctl Parameters: struct kvm_dirty_log (in) Returns: 0 on success, -1 on error
@@ -4799,7 +4799,7 @@ and injected exceptions. 7.18 KVM_CAP_MANUAL_DIRTY_LOG_PROTECT -Architectures: all +Architectures: x86, arm, arm64, mips Parameters: args[0] whether feature should be enabled or not With this capability enabled, KVM_GET_DIRTY_LOG will not automatically
Signature · 1 line
2.20.1
Quoted 4 lines · On Mon, 29 Apr 2019 10:27:10 +0200 Andrew Jones <[email protected]> wrote:
KVM_GET_DIRTY_LOGis implemented by all architectures, not just x86, andKVM_CAP_MANUAL_DIRTY_LOG_PROTECTis additionally implemented by arm, arm64, and mips.
Quoted 8 lines
Signed-off-by Andrew Jones <[email protected]>---
I skimmed all ioctls in the document to see if others needed to be fixed, but from my quick skim the only dirty ones seem to be the dirty log ones.Documentation/virtual/kvm/api.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
Quoted 9 lines · Andrew Jones
KVM_GET_DIRTY_LOGis implemented by all architectures, not just x86, andKVM_CAP_MANUAL_DIRTY_LOG_PROTECTis additionally implemented by arm, arm64, and mips.Signed-off-by Andrew Jones <[email protected]>---
I skimmed all ioctls in the document to see if others needed to be fixed, but from my quick skim the only dirty ones seem to be the dirty log ones.
Queued, thanks!
Paolo
Quoted 35 lines
Documentation/virtual/kvm/api.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)Documentation/virtual/kvm/api.txt +3
-3@@ -321,7 +321,7 @@ cpu's hardware control block. 4.8 KVM_GET_DIRTY_LOG (vm ioctl) Capability: basic -Architectures: x86 +Architectures: all Type: vm ioctl Parameters: struct kvm_dirty_log (in/out) Returns: 0 on success, -1 on error@@ -3810,7 +3810,7 @@ to I/O ports. 4.117 KVM_CLEAR_DIRTY_LOG (vm ioctl) Capability: KVM_CAP_MANUAL_DIRTY_LOG_PROTECT -Architectures: x86 +Architectures: x86, arm, arm64, mips Type: vm ioctl Parameters: struct kvm_dirty_log (in) Returns: 0 on success, -1 on error@@ -4799,7 +4799,7 @@ and injected exceptions. 7.18 KVM_CAP_MANUAL_DIRTY_LOG_PROTECT -Architectures: all +Architectures: x86, arm, arm64, mips Parameters: args[0] whether feature should be enabled or not With this capability enabled, KVM_GET_DIRTY_LOG will not automatically