Lines Matching +refs:debug +refs:get +refs:op

719     configuration (if there is) is not corrupted. Userspace can get a copy
1322 Reads debug registers from the vcpu.
1344 Writes debug registers into the vcpu.
1483 The capability that is supposed to get enabled.
2119 the kernel will ignore the length of guest write and may get a faster vmexit.
2891 LoongArch csr registers are used to control guest cpu or get status of guest
3693 Set up the processor specific debug registers and configure vcpu for
3694 handling guest debug events. There are two parts to the structure, the
3695 first a control bitfield indicates the type of debug events to handle
3706 - KVM_GUESTDBG_USE_HW: using hardware debug events [arm64]
3720 typically contains a set of debug registers.
3722 For arm64 the number of debug registers is implementation defined and
3728 the single-step debug event (KVM_GUESTDBG_SINGLESTEP) is supported.
3733 When debug events exit the main run loop with the reason
3735 structure containing architecture specific debug information.
3833 __u32 op; /* type of operation */
3857 The type of operation is specified in the "op" field. Flags modifying
3940 occurred. The cmpxchg op is permitted for the VM ioctl if
3967 This ioctl is used to get guest storage key values on the s390
3979 you want to get.
3982 whose storage keys to get. The count field must be at least 1 and the maximum
4006 whose storage keys to get. The count field must be at least 1 and the maximum
4591 This ioctl is used to get the values of the CMMA bits on the s390
5070 userspace should not expect to get any particular value there.
6146 __u8 op; /* operation to perform */
6163 The type of operation is specified in the "op" field.
6347 Note, there is no "get" API. Userspace is responsible for explicitly tracking
6604 } debug;
6606 If the exit_reason is KVM_EXIT_DEBUG, then a vcpu is processing a debug event
7551 get handled by the kernel or not. Enabling or disabling in-kernel
8341 The dirty ring can get full. When it happens, the KVM_RUN of the
8633 Future versions of kvm may implement additional events. These will get
8662 This capability indicates if the flic device will be able to get/set the
8794 instead get bounced to user space through the KVM_EXIT_X86_RDMSR and
8895 they will get passed on to user space. So user space still has to have
8938 This new attribute allows to get, set or clear the Modified Change