Lines Matching refs:userspace
116 is discouraged if userspace memory allocation (KVM_CAP_USER_MEMORY) is
178 The KVM_RUN ioctl (cf.) communicates with userspace via a shared
224 allocation of vcpu ids. For example, if userspace wants
736 blobs in userspace. When the guest writes the MSR, kvm copies one
902 __u64 userspace_addr; /* start of the userspace allocated memory */
928 posted to userspace as KVM_EXIT_MMIO exits.
1031 in-kernel irqchip, the multiprocessing state must be maintained by userspace on
1051 in-kernel irqchip, the multiprocessing state must be maintained by userspace on
1103 This ioctl would copy current vcpu's xsave struct to the userspace.
1118 This ioctl would copy userspace's xsave struct to the kernel.
1142 This ioctl would copy current vcpu's xcrs to the userspace.
1166 This ioctl would set vcpu's xcr to the value userspace specified.
1201 hardware, kernel, and userspace capabilities, and with user requirements (for
1241 feature in userspace, then you can enable the feature for KVM_SET_CPUID2.
1612 This must be called whenever userspace has changed an entry in the shared
1615 The "bitmap" field is the userspace address of an array. This array
1640 Allows userspace to mask PCI INTx interrupts from the assigned device. The
1648 When modifying the INTx disable state, userspace should precede updating the
1693 liobns will cause a vm exit and must be handled by userspace.
1696 to map the created TCE table into userspace. This lets userspace read
1698 userspace update the TCE table directly which is useful in some
1723 to map the allocated RMA into userspace. The mapped area can then be
2096 userspace. The host will set a flag in the pvclock structure that is checked
2211 This can in turn be used by userspace to generate the appropriate
2229 be used regardless of how they are backed by userspace.
2489 __u64 addr; /* userspace address of attr data */
2642 calls by the guest for that service will be passed to userspace to be
2704 The member 'flags' is used for passing flags from userspace.
2779 __u64 buf; /* buffer in userspace */
2797 supplied by the userspace application where the read data should be written
2930 This ioctl allows userspace to retrieve the complete state of all currently
2933 userspace buffer and its length:
2945 If -ENOBUFS is returned the buffer provided was too small and userspace
2961 This ioctl allows userspace to set the complete state of all cpu-local
2963 interrupt state after a migration. The input parameter is a userspace buffer
2972 The userspace memory referenced by buf contains a struct kvm_s390_irq
3098 operations are complete (and guest state is consistent) only after userspace
3113 Unused. This was once used for 'hypercall to userspace'. To implement
3256 As with SHUTDOWN, userspace can choose to ignore the request, or
3264 * shared registers between kvm and userspace.
3266 * kvm_dirty_regs specified the register classes dirtied by userspace
3277 If KVM_CAP_SYNC_REGS is defined, these fields allow userspace to access
3279 avoid some system call overhead if userspace has to handle the exit.
3364 between userspace and KVM. The "params" and "array" fields are userspace
3367 userspace has reserved for the array. It must be at least the size dictated
3371 contents are undefined, and any modification by userspace results in
3375 the guest's TLB. If userspace makes any changes, it must call KVM_DIRTY_TLB
3402 handled in-kernel, while the other I/O instructions are passed to userspace.
3510 not to attempt to handle the hcall, but will always exit to userspace
3513 userspace from doing that.
3558 Before exiting to userspace, kvm handlers should fill in s390_stsi field of
3575 KVM handlers should exit to userspace with rc = -EREMOTE.