Home
last modified time | relevance | path

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

/openbmc/linux/tools/testing/selftests/kvm/include/
H A Dkvm_util_base.h353 vm_ioctl(vm, KVM_GET_DIRTY_LOG, &args); in kvm_vm_get_dirty_log()
/openbmc/qemu/linux-headers/linux/
H A Dkvm.h1465 #define KVM_GET_DIRTY_LOG _IOW(KVMIO, 0x42, struct kvm_dirty_log) macro
/openbmc/linux/include/uapi/linux/
H A Dkvm.h1469 #define KVM_GET_DIRTY_LOG _IOW(KVMIO, 0x42, struct kvm_dirty_log) macro
/openbmc/linux/tools/include/uapi/linux/
H A Dkvm.h1462 #define KVM_GET_DIRTY_LOG _IOW(KVMIO, 0x42, struct kvm_dirty_log) macro
/openbmc/linux/virt/kvm/
H A Dkvm_main.c4825 case KVM_GET_DIRTY_LOG: { in kvm_vm_ioctl()
5042 case KVM_GET_DIRTY_LOG: { in kvm_vm_compat_ioctl()
/openbmc/linux/Documentation/virt/kvm/
H A Dapi.rst322 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 to
7345 With KVM_DIRTY_LOG_MANUAL_PROTECT_ENABLE is set, KVM_GET_DIRTY_LOG will not
7355 large amount of time can pass between a call to KVM_GET_DIRTY_LOG and
8194 KVM_GET_DIRTY_LOG interface in that, when reading the dirty ring from
8197 flushing is done by the KVM_GET_DIRTY_LOG ioctl). To achieve that, one
8225 KVM_GET_DIRTY_LOG ioctl. KVM_CLEAR_DIRTY_LOG isn't needed as long as all
/openbmc/qemu/accel/kvm/
H A Dkvm-all.c619 ret = kvm_vm_ioctl(s, KVM_GET_DIRTY_LOG, &d); in kvm_slot_get_dirty_log()