On 29/04/19 10:27, Andrew Jones wrote: > 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. > > Signed-off-by: Andrew Jones <drjones@xxxxxxxxxx> > --- > 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 > Documentation/virtual/kvm/api.txt | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt > index 67068c47c591..7f3ebc9e7cee 100644 > --- a/Documentation/virtual/kvm/api.txt > +++ b/Documentation/virtual/kvm/api.txt > @@ -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 >
