| /linux/virt/kvm/ |
| H A D | Makefile.kvm | 6 KVM ?= ../../../virt/kvm
8 kvm-y := $(KVM)/kvm_main.o $(KVM)/eventfd.o $(KVM)/binary_stats.o
9 kvm-$(CONFIG_KVM_VFIO) += $(KVM)/vfio.o
10 kvm-$(CONFIG_KVM_MMIO) += $(KVM)/coalesced_mmio.o
11 kvm-$(CONFIG_KVM_ASYNC_PF) += $(KVM)/async_pf.o
12 kvm-$(CONFIG_HAVE_KVM_IRQ_ROUTING) += $(KVM)/irqchip.o
13 kvm-$(CONFIG_HAVE_KVM_DIRTY_RING) += $(KVM)/dirty_ring.o
14 kvm-$(CONFIG_HAVE_KVM_PFNCACHE) += $(KVM)/pfncache.o
15 kvm-$(CONFIG_KVM_PRIVATE_MEM) += $(KVM)/guest_memfd.o
|
| /linux/Documentation/process/ |
| H A D | maintainer-kvm-x86.rst | 3 KVM x86
8 KVM strives to be a welcoming community; contributions from newcomers are
12 an honest effort to follow KVM x86's guidelines, are receptive to feedback,
22 KVM x86 is currently in a transition period from being part of the main KVM
23 tree, to being "just another KVM arch". As such, KVM x86 is split across the
24 main KVM tree, ``git.kernel.org/pub/scm/virt/kvm/kvm.git``, and a KVM x86
28 main KVM tree, while all development for the next cycle is routed through the
29 KVM x86 tree. In the unlikely event that a fix for the current cycle is routed
30 through the KVM x86 tree, it will be applied to the ``fixes`` branch before
31 making its way to the main KVM tree.
[all …]
|
| /linux/Documentation/translations/sp_SP/process/ |
| H A D | maintainer-kvm-x86.rst | 6 KVM x86
11 KVM se esfuerza por ser una comunidad acogedora; las contribuciones de los
16 seguir las directrices de KVM x86, sea receptivo a los comentarios, y
27 KVM x86 se encuentra actualmente en un período de transición de ser parte
28 del árbol principal de KVM, a ser "sólo otra rama de KVM". Como tal, KVM
29 x86 está dividido entre el árbol principal de KVM,
30 ``git.kernel.org/pub/scm/virt/kvm/kvm.git``, y un árbol específico de KVM
34 directamente al árbol principal de KVM, mientras que todo el desarrollo
35 para el siguiente ciclo se dirige a través del árbol de KVM x86. En el
37 través del árbol KVM x86, se aplicará a la rama ``fixes`` antes de llegar
[all …]
|
| /linux/Documentation/arch/s390/ |
| H A D | vfio-ap-locking.rst | 35 The KVM Lock (include/linux/kvm_host.h)
46 The KVM Lock (kvm->lock) controls access to the state data for a KVM guest. This
50 The KVM pointer is stored in the in the matrix_mdev instance
52 been attached to the KVM guest.
69 KVM guest. This lock must be held:
71 1. To control access to the KVM pointer (matrix_mdev->kvm) while the vfio_ap
72 device driver is using it to plug/unplug AP devices passed through to the KVM
78 AP devices passed through to a KVM guest.
81 if the adapter is passed through to a KVM guest, it will have to be
84 found. The KVM pointer (matrix_mdev->kvm) can then be used to determine if
[all …]
|
| 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:
131 to the KVM guest. Each bit in the mask, from left to right, corresponds to
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.
141 assigned to the KVM guest. The ADM bit mask controls which domains can be
198 1. Provides the interfaces to secure APQNs for exclusive use of KVM guests.
202 domains, and control domains comprising the matrix for a KVM guest.
205 by a KVM guest's SIE state description to grant the guest access to a matrix
[all …]
|
| /linux/Documentation/virt/kvm/x86/ |
| H A D | running-nested-guests.rst | 4 Running nested guests with KVM
8 can be KVM-based or a different hypervisor). The straightforward
9 example is a KVM guest that in turn runs on a KVM guest (the rest of
20 | KVM (/dev/kvm) |
24 | KVM (/dev/kvm) |
31 - L0 – level-0; the bare metal host, running KVM
34 hypervisor", as it itself is capable of running KVM.
56 There are several scenarios where nested KVM can be useful, to name a
61 Provider, using nested KVM lets you rent a large enough "guest
79 From Linux kernel v4.20 onwards, the ``nested`` KVM parameter is enabled
[all …]
|
| 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.
|
| /linux/Documentation/virt/kvm/arm/ |
| H A D | fw-pseudo-registers.rst | 7 KVM handles the hypercall services as requested by the guests. New hypercall
8 services are regularly made available by the ARM specification or by KVM (as
11 This means that a guest booted on two different versions of KVM can observe
17 In order to remedy this situation, KVM exposes a set of "firmware
26 KVM implements the PSCI (Power State Coordination Interface)
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
[all …]
|
| H A D | hypercalls.rst | 4 KVM/arm64-specific hypercalls exposed to guests
7 This file documents the KVM/arm64-specific hypercalls which may be
8 exposed by KVM/arm64 to guest operating systems. These hypercalls are
14 All KVM/arm64-specific hypercalls are allocated within the "Vendor
18 order to determine that the KVM/arm64-specific hypercalls are available.
23 Provides a discovery mechanism for other KVM/arm64 hypercalls.
26 | Presence: | Mandatory for the KVM/arm64 UID |
73 Share a region of memory with the KVM host, granting it read, write and execute
98 Revoke access permission from the KVM host to a memory region previously shared
124 allowing accesses to this region to be emulated by the KVM host. The size of the
|
| H A D | vcpu-features.rst | 7 KVM/arm64 provides two mechanisms that allow userspace to configure
18 Otherwise, all CPU features supported by KVM are described by the architected
25 of architectural features supported by the CPU implementation. KVM initializes
27 system. The ID register values may be VM-scoped in KVM, meaning that the
30 KVM allows userspace to *opt-out* of certain CPU features described by the ID
40 scheme for fields in ID register'. KVM does not allow ID register values that
45 before accessing the rest of the vCPU's CPU register state. KVM may use the
|
| /linux/arch/powerpc/kvm/ |
| H A D | Kconfig | 3 # KVM configuration
20 config KVM config
48 tristate "KVM support for PowerPC book3s_32 processors"
51 select KVM
65 tristate "KVM support for PowerPC book3s_64 processors"
68 select KVM
82 tristate "KVM for POWER7 and later using hypervisor mode in host"
92 If you say Y here, KVM will use the hardware virtualization
96 that KVM is not usable under PowerVM (pHyp), is only usable
103 tristate "KVM support without using hypervisor mode in host"
[all …]
|
| /linux/Documentation/virt/kvm/s390/ |
| H A 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 …]
|
| /linux/arch/s390/kvm/ |
| H A D | Kconfig | 3 # KVM configuration
9 prompt "KVM"
19 config KVM config
21 prompt "Kernel-based Virtual Machine (KVM) support"
48 depends on KVM
50 Allow CAP_SYS_ADMIN users to create KVM virtual machines that are
|
| /linux/arch/arm64/kvm/ |
| H A D | Kconfig | 3 # KVM configuration
20 menuconfig KVM config
21 bool "Kernel-based Virtual Machine (KVM) support"
48 depends on KVM
50 Say Y here to enable the debug mode for the non-VHE KVM EL2 object.
57 bool "Protected KVM hypervisor stacktraces"
71 depends on KVM
|
| /linux/Documentation/virt/kvm/loongarch/ |
| H A D | hypercalls.rst | 7 KVM hypercalls use the HVCL instruction with code 0x100 and the hypercall
16 To determine if the host is running on KVM, we can utilize the cpucfg()
24 On a KVM-virtualized Linux system, a read operation on cpucfg() at index
25 CPUCFG_KVM_BASE (0x40000000) returns the magic string 'KVM\0'.
28 capable KVM, you may now use hypercalls as described below.
30 KVM hypercall ABI
33 The KVM hypercall ABI is simple, with one scratch register a0 (v0) and at most
63 KVM Hypercalls Documentation
|
| /linux/Documentation/virt/kvm/devices/ |
| H A D | vfio.rst | 15 VM, KVM should be updated about their presence. When registered with
16 KVM, a reference to the VFIO file is held by KVM.
23 KVM_DEV_VFIO_FILE_ADD: Add a VFIO file (group/device) to VFIO-KVM device
29 KVM_DEV_VFIO_FILE_DEL: Remove a VFIO file (group/device) from VFIO-KVM
41 allocated by sPAPR KVM.
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A 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/arch/mips/kvm/ |
| H A D | Kconfig | 3 # KVM configuration
18 config KVM config
19 tristate "Kernel-based Virtual Machine (KVM) support"
35 depends on KVM
|
| /linux/Documentation/translations/zh_CN/mm/ |
| H A D | hwpoison.rst | 45 现在主要目标是KVM客户机，但它适用于所有类型的应用程序。支持KVM需要最近的qemu-kvm
48 对于KVM的使用，需要一个新的信号类型，这样KVM就可以用适当的地址将机器检查注入到客户
62 应用程序以温和的方式处理内存错误（例如，放弃受影响的对象） 这是KVM qemu使用的
|
| /linux/Documentation/virt/kvm/ |
| H A 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 …]
|
| /linux/Documentation/translations/zh_CN/arch/arm64/ |
| H A D | perf.rst | 54 这些属性分别排除了 KVM 宿主机和客户机。
56 KVM 宿主机可能运行在 EL0（用户空间），EL1（non-VHE 内核）和
59 KVM 客户机可能运行在 EL0（用户空间）和 EL1（内核）。
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-intel-pt.txt | 1346 $ ps -eLl | grep 'KVM\|PID'
1348 3 S 64055 1430 1 1440 1 80 0 - 1921718 - ? 00:02:47 CPU 0/KVM
1349 3 S 64055 1430 1 1441 1 80 0 - 1921718 - ? 00:02:41 CPU 1/KVM
1350 3 S 64055 1430 1 1442 1 80 0 - 1921718 - ? 00:02:38 CPU 2/KVM
1351 3 S 64055 1430 1 1443 2 80 0 - 1921718 - ? 00:03:18 CPU 3/KVM
1368 CPU 0/KVM 1440 ffffffff82133cdd __vmx_vcpu_run+0x3d ([kernel.kallsyms]) movq 0x48(%rax), %r9
1369 CPU 0/KVM 1440 ffffffff82133ce1 __vmx_vcpu_run+0x41 ([kernel.kallsyms]) movq 0x50(%rax), %r10
1370 CPU 0/KVM 1440 ffffffff82133ce5 __vmx_vcpu_run+0x45 ([kernel.kallsyms]) movq 0x58(%rax), %r11
1371 CPU 0/KVM 1440 ffffffff82133ce9 __vmx_vcpu_run+0x49 ([kernel.kallsyms]) movq 0x60(%rax), %r12
1372 CPU 0/KVM 144
[all...] |
| /linux/Documentation/translations/zh_TW/arch/arm64/ |
| H A D | perf.rst | 55 這些屬性分別排除了 KVM 宿主機和客戶機。
57 KVM 宿主機可能運行在 EL0（用戶空間），EL1（non-VHE 內核）和
60 KVM 客戶機可能運行在 EL0（用戶空間）和 EL1（內核）。
|
| /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
|