Lines Matching refs:KVM

1 The Definitive KVM (Kernel-based Virtual Machine) API Documentation
51 As of Linux 2.6.22, the KVM ABI has been stabilized: no backward
69   Capability: which KVM extension provides this ioctl.  Can be 'basic',
646 (active-low/active-high) for level-triggered interrupts, and KVM used
924 KVM_MEM_READONLY.  The former can be set to instruct KVM to keep track of
1627 The "num_dirty" field is a performance hint for KVM to determine whether it
1713 will be accessed by real-mode (MMU off) accesses in a KVM guest.
2047 MIPS KVM control registers (see above) have the following id bit patterns:
2210 the "Server" class MMU emulation supported by KVM.
2517 This tells KVM what type of CPU to present to the guest, and what
2550 This queries KVM for preferred CPU target type which can be emulated
2551 by KVM on underlying host.
2678 correctly trapped and the KVM run loop exits at the breakpoint and not
2804 KVM with the currently defined set of flags.
3168 Deprecated - was used for 440 KVM.
3364 between userspace and KVM.  The "params" and "array" fields are userspace
3370 While KVM_RUN is active, the shared region is under control of KVM.  Its
3376 to tell KVM which entries have been changed, prior to calling KVM_RUN again
3464 Config5.FRE bits are accessible via the KVM API and also from the guest,
3476 accessed, and the Config5.MSAEn bit is accessible via the KVM API and also from
3512 disable others of a group of related hcalls, but KVM does not prevent
3555 initial handling in the kernel, KVM exits to user space with
3575 KVM handlers should exit to userspace with rc = -EREMOTE.
3582 features of the KVM implementation.