| /openbmc/linux/arch/riscv/kvm/ |
| H A D | Kconfig | 3 # KVM configuration
20 config KVM config
21 tristate "Kernel-based Virtual Machine (KVM) support (EXPERIMENTAL)"
|
| /openbmc/qemu/hw/intc/ |
| H A D | Kconfig | 27 select ARM_GIC_KVM if KVM
36 depends on ARM_GIC && KVM
52 depends on S390_FLIC && KVM
|
| /openbmc/linux/drivers/vfio/pci/ |
| H A D | Kconfig | 52 bool "VFIO PCI extensions for s390x KVM passthrough"
53 depends on S390 && KVM
57 to KVM passthrough capabilities, such as interpretive execution of
60 To enable s390x KVM vfio-pci extensions, say Y.
|
| /openbmc/qemu/docs/system/i386/ |
| H A D | hyperv.rst | 8 In some cases when implementing a hardware interface in software is slow, KVM
14 KVM on x86 implements Hyper-V Enlightenments for Windows guests. These features
22 No Hyper-V enlightenments are enabled by default by either KVM or QEMU. In
33 identification (CPUID 0x40000000..0x4000000A) to Hyper-V. KVM identification
149 with ``hv-frequencies``, allows Hyper-V on KVM to pass stable clocksource
152 Note, KVM doesn't fully support re-enlightenment notifications and doesn't
162 implements paravirtualized protocol between L0 (KVM) and L1 (Hyper-V)
193 When the option is set to 'auto' QEMU will enable the feature only when KVM
230 enabled, it allows L0 (KVM) and L1 (Hyper-V) hypervisors to collaborate to
240 for faster hypercalls processing as KVM can avoid reading guest's memory.
[all …]
|
| H A D | xen.rst | 8 KVM has support for hosting Xen guests, intercepting Xen hypercalls and event
10 run under Xen to be hosted in QEMU under Linux/KVM instead.
17 Xen mode is enabled by setting the ``xen-version`` property of the KVM
32 0x40000000..0x4000000A) to Xen. The KVM identification and features are not
39 The following properties exist on the KVM accelerator object:
140 The minimal Xen support in the KVM accelerator requires the host to be running
|
| /openbmc/linux/tools/perf/Documentation/ |
| H A D | perf-intel-pt.txt | 1288 $ ps -eLl | grep 'KVM\|PID'
1290 3 S 64055 1430 1 1440 1 80 0 - 1921718 - ? 00:02:47 CPU 0/KVM
1291 3 S 64055 1430 1 1441 1 80 0 - 1921718 - ? 00:02:41 CPU 1/KVM
1292 3 S 64055 1430 1 1442 1 80 0 - 1921718 - ? 00:02:38 CPU 2/KVM
1352 $ ps -eLl | grep 'KVM\|PID'
1512 CPU 0/KVM 0 [000] 0.000000: PERF_RECORD_COMM: CPU 0/KVM:13376/13381
1513 CPU 1/KVM 0 [000] 0.000000: PERF_RECORD_COMM: CPU 1/KVM:13376/13382
1514 CPU 2/KVM 0 [000] 0.000000: PERF_RECORD_COMM: CPU 2/KVM:13376/13383
1515 CPU 3/KVM 0 [000] 0.000000: PERF_RECORD_COMM: CPU 3/KVM:13376/13384
1610 A common case for KVM test programs is that the test program acts as the
[all …]
|
| /openbmc/qemu/docs/devel/ |
| H A D | multi-process.rst | 141 directly inject interrupts into the VM via the KVM driver, again,
143 The QEMU virtio setup code configures the KVM driver with an eventfd
598 The expanded idea would require a new type of KVM device:
681 with the KVM driver.
686 KVM an access map telling it which areas of the image have no
689 the KVM drive which size accesses are allowed to the image.
696 *KVM\_CREATE\_DEVICE* ``ioctl()`` with a *KVM\_DEV\_TYPE\_USER* type.
698 KVM\_DEV\_TYPE\_USER device ops
709 This routine is called when QEMU issues a *KVM\_CREATE\_DEVICE*
778 A *KVM\_DEV\_USER\_SHADOW\_SIZE* ``ioctl()`` causes the KVM driver to
[all …]
|
| /openbmc/linux/Documentation/virt/kvm/x86/ |
| H A D | hypercalls.rst | 4 Linux KVM Hypercall
8 KVM Hypercalls have a three-byte sequence of either the vmcall or the vmmcall
24 For further information on the S390 diagnose call as supported by KVM,
31 KVM hypercalls uses 4 byte opcode, that are patched with 'hypercall-instructions'
36 KVM hypercalls use the HYPCALL instruction with code 0 and the hypercall
40 KVM Hypercalls Documentation
73 OR KVM specific enumeration mechanism (which is this hypercall)
177 :Purpose: Request KVM to map a GPA range with the specified attributes.
|
| H A D | cpuid.rst | 4 KVM CPUID bits
11 mask-out some, or even all KVM-related cpuid features before launching
14 KVM cpuid functions are:
30 This function queries the presence of KVM cpuid leafs.
|
| H A D | nested-vmx.rst | 10 On Intel processors, KVM uses Intel's VMX (Virtual-Machine eXtensions)
31 Single-level virtualization has two levels - the host (KVM) and the guests.
32 In nested virtualization, we have three levels: The host (KVM), which we call
63 which are used in practice by popular hypervisors (KVM and others).
70 Still, for debugging purposes, KVM developers might be interested to know the
79 of this structure changes, this can break live migration across KVM versions.
|
| /openbmc/linux/tools/kvm/kvm_stat/ |
| H A D | kvm_stat.txt | 6 kvm_stat - Report KVM kernel module event counters
15 kvm_stat prints counts of KVM kernel module trace events. These events signify
25 The set of KVM kernel module trace events may be specific to the kernel version
26 or architecture. It is best to check the KVM kernel module source code for the
|
| /openbmc/qemu/hw/i386/ |
| H A D | Kconfig | 7 depends on KVM
11 depends on KVM
143 depends on KVM && (I386 || X86_64)
|
| /openbmc/bmcweb/redfish-core/include/generated/enums/ |
| H A D | operating_system.hpp | 26 KVM, enumerator
69 {VirtualMachineEngineTypes::KVM, "KVM"},
|
| /openbmc/linux/Documentation/arch/s390/ |
| H A D | vfio-ap.rst | 14 is to make AP cards available to KVM guests using the VFIO mediated device
128 control domains assigned to the KVM guest:
133 use by the KVM guest.
136 assigned to the KVM guest. Each bit in the mask, from left to right,
138 corresponding queue is valid for use by the KVM guest.
208 Reserve APQNs for exclusive use of KVM guests
249 The process for reserving an AP queue for use by a KVM guest is:
408 KVM structure used to configure the KVM guest is provided via this callback.
547 * KVM
555 * KVM
[all …]
|
| /openbmc/linux/Documentation/virt/kvm/arm/ |
| H A D | hyp-abi.rst | 9 KVM). It doesn't cover the interaction of the kernel with the
10 hypervisor when running as a guest (under Xen, KVM or any other
14 Note: KVM/arm has been removed from the kernel. The API described
16 booted at HYP. It can also be used by a hypervisor other than KVM
|
| /openbmc/linux/Documentation/virt/kvm/s390/ |
| H A D | s390-pv-boot.rst | 17 KVM to decrypt the protected virtual machine.
19 Based on this data, KVM will make the protected virtual machine known
22 hashes, to ensure integrity. Afterwards KVM can run the PVM via the
23 SIE instruction which the UV will intercept and execute on KVM's
|
| H A D | index.rst | 4 KVM for s390 systems
|
| /openbmc/linux/virt/kvm/ |
| H A D | Kconfig | 2 # KVM common configuration items and defaults
73 depends on KVM && COMPAT && !(S390 || ARM64 || RISCV)
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | entry.rst | 1 Entry/exit handling for exceptions, interrupts, syscalls and KVM
15 the transition type sections: `Syscalls`_, `KVM`_, `Interrupts and regular
111 KVM chapter
118 kvm_guest_enter_irqoff() is a KVM-specific variant of exit_to_user_mode()
119 and kvm_guest_exit_irqoff() is the KVM variant of enter_from_user_mode().
126 Do not nest KVM entry/exit transitions because doing so is nonsensical.
132 and KVM transitions.
|
| /openbmc/qemu/hw/remote/ |
| H A D | Kconfig | 3 depends on PCI && PCI_EXPRESS && KVM
|
| /openbmc/qemu/ui/ |
| H A D | qemu.desktop | 7 Keywords=Emulators;Virtualization;KVM;
|
| /openbmc/linux/Documentation/virt/kvm/ |
| H A D | api.rst | 56 model that is supported by KVM.
3487 by KVM on underlying host.
5595 be intercepted by KVM.
6357 Deprecated - was used for 440 KVM.
6959 KVM API and also from the guest.
7386 notifies KVM when a guest requests to become a secure guest, and KVM
7629 quirks that can be disabled in KVM.
7743 features of the KVM implementation.
7933 compatibility, KVM initializes this msr to KVM's internal vcpu index. When this
8024 handling by KVM (as some KVM hypercall may be mistakenly treated as TLB
[all …]
|
| /openbmc/qemu/docs/system/arm/ |
| H A D | virt.rst | 40 - running guests using the KVM accelerator on aarch64 hardware
63 - ``host`` (with KVM only)
67 - ``max`` (same as ``host`` for KVM; best possible emulation with TCG)
76 with KVM. You may also need to ensure your guest kernel is configured
129 Use the same GIC version the host provides, when using KVM
131 Use the best GIC version possible (same as host when using KVM;
|
| /openbmc/linux/Documentation/translations/zh_CN/dev-tools/ |
| H A D | gdb-kernel-debugging.rst | 14 此教程基于QEMU/KVM虚拟机，但文中示例也适用于其他gdb stub。
25 - 创建一个QEMU/KVM的linux虚拟机（详情请参考 www.linux-kvm.org 和 www.qemu.org ）。
37 - 启用QEMU/KVM的gdb stub，可以通过如下方式实现
|
| /openbmc/qemu/docs/system/ |
| H A D | barrier.rst | 10 or by installing a KVM software in the guest OS.
16 is a KVM (Keyboard-Video-Mouse) software forked from Symless's
|