virt/kvm/api.rst

719     configuration (if there is) is not corrupted. Userspace can get a copy
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.
2217   - check whether changing LINT1 will queue an NMI (see the LVT entry for LINT1)
2891 LoongArch csr registers are used to control guest cpu or get status of guest
3170 kvm_irqfd.resamplefd.  It is the user's responsibility to re-queue
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
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