Searched refs:KVM_GET_DIRTY_LOG (Results 1 – 5 of 5) sorted by relevance
353 vm_ioctl(vm, KVM_GET_DIRTY_LOG, &args); in kvm_vm_get_dirty_log()
1462 #define KVM_GET_DIRTY_LOG _IOW(KVMIO, 0x42, struct kvm_dirty_log) macro
1469 #define KVM_GET_DIRTY_LOG _IOW(KVMIO, 0x42, struct kvm_dirty_log) macro
4824 case KVM_GET_DIRTY_LOG: { in kvm_vm_ioctl()5041 case KVM_GET_DIRTY_LOG: { in kvm_vm_compat_ioctl()
322 4.8 KVM_GET_DIRTY_LOG (vm ioctl)333 /* for KVM_GET_DIRTY_LOG */1347 writes to memory within the slot. See KVM_GET_DIRTY_LOG ioctl to know how to7345 With KVM_DIRTY_LOG_MANUAL_PROTECT_ENABLE is set, KVM_GET_DIRTY_LOG will not7355 large amount of time can pass between a call to KVM_GET_DIRTY_LOG and8194 KVM_GET_DIRTY_LOG interface in that, when reading the dirty ring from8197 flushing is done by the KVM_GET_DIRTY_LOG ioctl). To achieve that, one8225 KVM_GET_DIRTY_LOG ioctl. KVM_CLEAR_DIRTY_LOG isn't needed as long as all
