Home
last modified time | relevance | path

Searched refs:KVM_GET_DIRTY_LOG (Results 1 – 6 of 6) sorted by relevance

/linux/tools/testing/selftests/kvm/s390/
H A Ducontrol_test.c229 rc = ioctl(self->vm_fd, KVM_GET_DIRTY_LOG, &dlog); in TEST_F()
/linux/include/uapi/linux/
H A Dkvm.h1263 #define KVM_GET_DIRTY_LOG _IOW(KVMIO, 0x42, struct kvm_dirty_log) macro
/linux/tools/include/uapi/linux/
H A Dkvm.h1254 #define KVM_GET_DIRTY_LOG _IOW(KVMIO, 0x42, struct kvm_dirty_log) macro
/linux/tools/testing/selftests/kvm/include/
H A Dkvm_util.h484 vm_ioctl(vm, KVM_GET_DIRTY_LOG, &args); in kvm_vm_get_dirty_log()
/linux/virt/kvm/
H A Dkvm_main.c5205 case KVM_GET_DIRTY_LOG: { in kvm_vm_ioctl()
5445 case KVM_GET_DIRTY_LOG: { in kvm_vm_compat_ioctl()
/linux/Documentation/virt/kvm/
H A Dapi.rst354 4.8 KVM_GET_DIRTY_LOG
365 /* for KVM_GET_DIRTY_LOG */
1415 writes to memory within the slot. See KVM_GET_DIRTY_LOG ioctl to know how to
8174 With KVM_DIRTY_LOG_MANUAL_PROTECT_ENABLE is set, KVM_GET_DIRTY_LOG will not
8184 large amount of time can pass between a call to KVM_GET_DIRTY_LOG and
8704 KVM_GET_DIRTY_LOG interface in that, when reading the dirty ring from
8707 flushing is done by the KVM_GET_DIRTY_LOG ioctl). To achieve that, one
8735 KVM_GET_DIRTY_LOG ioctl. KVM_CLEAR_DIRTY_LOG isn't needed as long as all