Lines Matching refs:kvm

7 The kvm API is a set of ioctls that are issued to control various aspects
11    whole kvm subsystem.  In addition a system ioctl is used to create
31 The kvm API is centered around file descriptors.  An initial
32 open("/dev/kvm") obtains a handle to the kvm subsystem; this handle
42 kinds of tricks are explicitly not supported by kvm.  While they will
57 Instead, kvm defines extension identifiers and a facility to query
65 This section describes ioctls that can be used to control kvm guests.
97 This identifies the API version as the stable kvm API. It is not
142 by kvm version and host processor, but does not change otherwise.  The
144 kvm adjusts nmsrs to reflect the actual number of msrs and fills in
147 Note: if kvm indicates supports MCE (KVM_CAP_MCE), then the MCE bank MSRs are
161 kvm API.  Userspace passes an extension identifier (an integer) and
355 /* ppc -- see arch/powerpc/include/uapi/asm/kvm.h */
495 kvm will fill in the 'data' member.
747 blobs in userspace.  When the guest writes the MSR, kvm copies one
1231 and kvm.  Userspace can use the information returned by this ioctl to
1247 x2apic), may not be present in the host cpu, but are exposed by kvm if it can
2190 kvm-pit/<owner-process-pid>
2763 kvm.Userspace can use the information returned by this ioctl to query
2764 which features are emulated by kvm instead of being present natively.
2776 which kvm emulates, as returned by the CPUID instruction, with unknown
2780 but are exposed by kvm in KVM_GET_SUPPORTED_CPUID because they can be
3124 executed a port I/O instruction which could not be satisfied by kvm.
3126 where kvm expects application code to place the data for the next
3147 by kvm.  The 'data' member contains the written data if 'is_write' is
3339 	 * shared registers between kvm and userspace.
3633 Before exiting to userspace, kvm handlers should fill in s390_stsi field of