Searched refs:KVM_GET_DIRTY_LOG (Results 1 – 5 of 5) sorted by relevance
231 rc = ioctl(self->vm_fd, KVM_GET_DIRTY_LOG, &dlog); in TEST_F()
548 /* for KVM_GET_DIRTY_LOG */1215 #define KVM_GET_DIRTY_LOG _IOW(KVMIO, 0x42, struct kvm_dirty_log) macro
522 /* for KVM_GET_DIRTY_LOG */1188 #define KVM_GET_DIRTY_LOG _IOW(KVMIO, 0x42, struct kvm_dirty_log) macro
5192 case KVM_GET_DIRTY_LOG: { in kvm_vm_ioctl() 5432 case KVM_GET_DIRTY_LOG: { in kvm_vm_compat_ioctl()
354 4.8 KVM_GET_DIRTY_LOG365 /* for KVM_GET_DIRTY_LOG */1404 writes to memory within the slot. See KVM_GET_DIRTY_LOG ioctl to know how to7967 With KVM_DIRTY_LOG_MANUAL_PROTECT_ENABLE is set, KVM_GET_DIRTY_LOG will not7977 large amount of time can pass between a call to KVM_GET_DIRTY_LOG and8489 KVM_GET_DIRTY_LOG interface in that, when reading the dirty ring from8492 flushing is done by the KVM_GET_DIRTY_LOG ioctl). To achieve that, one8520 KVM_GET_DIRTY_LOG ioctl. KVM_CLEAR_DIRTY_LOG isn't needed as long as all