| /Linux-v5.15/arch/s390/kvm/ |
| D | Makefile | 6 KVM := ../../../virt/kvm macro
7 common-objs = $(KVM)/kvm_main.o $(KVM)/eventfd.o $(KVM)/async_pf.o \
8 $(KVM)/irqchip.o $(KVM)/vfio.o $(KVM)/binary_stats.o
|
| D | Kconfig | 3 # KVM configuration
9 prompt "KVM"
19 config KVM config
21 prompt "Kernel-based Virtual Machine (KVM) support"
51 depends on KVM
53 Allow CAP_SYS_ADMIN users to create KVM virtual machines that are
|
| /Linux-v5.15/arch/x86/kvm/ |
| D | Kconfig | 3 # KVM configuration
21 config KVM config
22 tristate "Kernel-based Virtual Machine (KVM) support"
62 bool "Compile KVM with -Werror"
67 depends on KVM
71 Add -Werror to the build flags for KVM.
76 tristate "KVM for Intel (and compatible) processors support"
77 depends on KVM && IA32_FEAT_CTL
79 Provides support for KVM on processors equipped with Intel's VT
90 Enables KVM guests to create SGX enclaves.
[all …]
|
| D | Makefile | 10 KVM := ../../../virt/kvm macro
12 kvm-y += $(KVM)/kvm_main.o $(KVM)/coalesced_mmio.o \
13 $(KVM)/eventfd.o $(KVM)/irqchip.o $(KVM)/vfio.o \
14 $(KVM)/dirty_ring.o $(KVM)/binary_stats.o
15 kvm-$(CONFIG_KVM_ASYNC_PF) += $(KVM)/async_pf.o
|
| /Linux-v5.15/arch/arm64/kvm/ |
| D | Makefile | 8 KVM=../../../virt/kvm macro
13 kvm-y := $(KVM)/kvm_main.o $(KVM)/coalesced_mmio.o $(KVM)/eventfd.o \
14 $(KVM)/vfio.o $(KVM)/irqchip.o $(KVM)/binary_stats.o \
|
| D | Kconfig | 3 # KVM configuration
20 menuconfig KVM config
21 bool "Kernel-based Virtual Machine (KVM) support"
46 if KVM
53 Say Y here to enable the debug mode for the non-VHE KVM EL2 object.
59 endif # KVM
|
| /Linux-v5.15/arch/powerpc/kvm/ |
| D | Kconfig | 3 # KVM configuration
20 config KVM config
51 tristate "KVM support for PowerPC book3s_32 processors"
53 select KVM
67 tristate "KVM support for PowerPC book3s_64 processors"
70 select KVM
83 tristate "KVM for POWER7 and later using hypervisor mode in host"
93 If you say Y here, KVM will use the hardware virtualization
97 that KVM is not usable under PowerVM (pHyp), is only usable
104 tristate "KVM support without using hypervisor mode in host"
[all …]
|
| D | Makefile | 7 KVM := ../../../virt/kvm macro
9 common-objs-y = $(KVM)/kvm_main.o $(KVM)/eventfd.o $(KVM)/binary_stats.o
10 common-objs-$(CONFIG_KVM_VFIO) += $(KVM)/vfio.o
11 common-objs-$(CONFIG_KVM_MMIO) += $(KVM)/coalesced_mmio.o
128 kvm-objs-$(CONFIG_HAVE_KVM_IRQ_ROUTING) += $(KVM)/irqchip.o
|
| /Linux-v5.15/Documentation/virt/kvm/ |
| D | running-nested-guests.rst | 2 Running nested guests with KVM
6 can be KVM-based or a different hypervisor). The straightforward
7 example is a KVM guest that in turn runs on a KVM guest (the rest of
18 | KVM (/dev/kvm) |
22 | KVM (/dev/kvm) |
29 - L0 – level-0; the bare metal host, running KVM
32 hypervisor", as it itself is capable of running KVM.
54 There are several scenarios where nested KVM can be useful, to name a
59 Provider, using nested KVM lets you rent a large enough "guest
77 From Linux kernel v4.20 onwards, the ``nested`` KVM parameter is enabled
[all …]
|
| D | s390-diag.rst | 4 The s390 DIAGNOSE call on KVM
7 KVM on s390 supports the DIAGNOSE call for making hypercalls, both for
19 all supported DIAGNOSE calls need to be handled by either KVM or its
22 All DIAGNOSE calls supported by KVM use the RS-a format::
34 DIAGNOSE function codes not specific to KVM, please refer to the
38 DIAGNOSE function code 'X'500' - KVM virtio functions
45 virtio subfunctions depend on KVM's userspace. Generally, userspace
62 Handled by either userspace or KVM (ioeventfd case).
69 General register 4 contains a 64bit identifier for KVM usage (the
80 DIAGNOSE function code 'X'501 - KVM breakpoint
[all …]
|
| D | s390-pv.rst | 9 Protected virtual machines (PVM) are KVM VMs that do not allow KVM to
12 provides an API that can be used by PVMs and KVM to request management
16 transition into protected mode. On transition, KVM registers the guest
34 Interrupt injection is safeguarded by the Ultravisor. As KVM doesn't
47 been intercepted into KVM. The exceptions need to be a valid outcome
48 of an instruction emulation by KVM, e.g. we can never inject a
49 addressing exception as they are reported by SIE since KVM has no
55 KVM cannot intercept lctl(g) and lpsw(e) anymore in order to be
67 to interpret every instruction, but needs to hand some tasks to KVM;
103 emulation of the instruction with the data provided by KVM. That might
[all …]
|
| D | ppc-pv.rst | 4 The PPC KVM paravirtual interface
7 The basic execution principle by which KVM on PowerPC works is to run all kernel
24 To find out if we're running on KVM or not, we leverage the device tree. When
25 Linux is running on KVM, a node /hypervisor exists. That node contains a
28 Once you determined you're running under a PV capable KVM, you can now use
31 KVM hypercalls
57 apply for x86 and powerpc alike with the exception that each KVM hypercall
58 also needs to be ORed with the KVM vendor code which is (42 << 16).
75 map this shared page using the KVM hypercall KVM_HC_PPC_MAP_MAGIC_PAGE.
97 When mapping the magic page using the KVM hypercall KVM_HC_PPC_MAP_MAGIC_PAGE,
[all …]
|
| 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.
|
| /Linux-v5.15/Documentation/virt/kvm/arm/ |
| D | psci.rst | 7 KVM implements the PSCI (Power State Coordination Interface)
12 and KVM implements these updates if they make sense from a virtualization
15 This means that a guest booted on two different versions of KVM can
21 In order to remedy this situation, KVM exposes a set of "firmware
33 highest PSCI version implemented by KVM and compatible with v0.2)
34 - Allows any PSCI version implemented by KVM and compatible with
40 offered by KVM to the guest via a HVC call. The workaround is described
46 KVM does not offer
58 offered by KVM to the guest via a HVC call. The workaround is described
65 available. KVM does not offer firmware support for the workaround.
[all …]
|
| /Linux-v5.15/Documentation/virt/kvm/devices/ |
| D | vfio.rst | 14 are enabled and disabled for use by the VM, KVM should be updated
15 about their presence. When registered with KVM, a reference to the
16 VFIO-group is held by KVM.
22 KVM_DEV_VFIO_GROUP_ADD: Add a VFIO group to VFIO-KVM device tracking
25 KVM_DEV_VFIO_GROUP_DEL: Remove a VFIO group from VFIO-KVM device tracking
29 allocated by sPAPR KVM.
|
| /Linux-v5.15/arch/mips/kvm/ |
| D | Kconfig | 3 # KVM configuration
18 config KVM config
19 tristate "Kernel-based Virtual Machine (KVM) support"
35 depends on KVM
|
| /Linux-v5.15/Documentation/admin-guide/hw-vuln/ |
| D | multihit.rst | 81 * - KVM: Mitigation: Split huge pages
83 * - KVM: Mitigation: VMX unsupported
84 - KVM is not vulnerable because Virtual Machine Extensions (VMX) is not supported.
85 * - KVM: Mitigation: VMX disabled
86 - KVM is not vulnerable because Virtual Machine Extensions (VMX) is disabled.
87 * - KVM: Vulnerable
111 In order to mitigate the vulnerability, KVM initially marks all huge pages
115 If EPT is disabled or not available on the host, KVM is in control of TLB
119 (non-nested) page tables. For simplicity, KVM will make large pages
122 Mitigation control on the kernel command line and KVM - module parameter
[all …]
|
| /Linux-v5.15/tools/testing/selftests/rcutorture/bin/ |
| D | kvm-end-run-stats.sh | 25 KVM="`pwd`/tools/testing/selftests/rcutorture"; export KVM
26 PATH=${KVM}/bin:$PATH; export PATH
|
| D | kvm.sh | 28 KVM="`pwd`/tools/testing/selftests/rcutorture"; export KVM
29 PATH=${KVM}/bin:$PATH; export PATH
36 TORTURE_INITRD="$KVM/initrd"; export TORTURE_INITRD
262 CONFIGFRAG=${KVM}/configs/${TORTURE_SUITE}; export CONFIGFRAG
272 resdir=$KVM/res
386 KVM="$KVM"; export KVM
569 -v KVM="$KVM" \
|
| D | kvm-check-branches.sh | 52 KVM="`pwd`/tools/testing/selftests/rcutorture"; export KVM
53 PATH=${KVM}/bin:$PATH; export PATH
|
| D | kvm-remote.sh | 22 KVM="`pwd`/tools/testing/selftests/rcutorture"; export KVM
23 PATH=${KVM}/bin:$PATH; export PATH
111 cp -a "$rundir" "$KVM/res/"
112 oldrun="$KVM/res/$ds"
|
| D | kvm-again.sh | 50 KVM="`pwd`/tools/testing/selftests/rcutorture"; export KVM
51 PATH=${KVM}/bin:$PATH; export PATH
|
| /Linux-v5.15/Documentation/translations/zh_CN/arm64/ |
| D | perf.rst | 54 这些属性分别排除了 KVM 宿主机和客户机。
56 KVM 宿主机可能运行在 EL0（用户空间），EL1（non-VHE 内核）和
59 KVM 客户机可能运行在 EL0（用户空间）和 EL1（内核）。
|
| /Linux-v5.15/Documentation/translations/zh_TW/arm64/ |
| D | perf.rst | 55 這些屬性分別排除了 KVM 宿主機和客戶機。
57 KVM 宿主機可能運行在 EL0（用戶空間），EL1（non-VHE 內核）和
60 KVM 客戶機可能運行在 EL0（用戶空間）和 EL1（內核）。
|
| /Linux-v5.15/tools/kvm/kvm_stat/ |
| 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
|
