Home
last modified time | relevance | path

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

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