Home
last modified time | relevance | path

Searched refs:KVM (Results 1 – 25 of 236) sorted by relevance

12345678910

/openbmc/linux/virt/kvm/
H A DMakefile.kvm6 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
/openbmc/qemu/target/ppc/
H A Dtrace-events4 kvm_failed_spr_set(int spr, const char *msg) "Warning: Unable to set SPR %d to KVM: %s"
6 kvm_failed_fpscr_set(const char *msg) "Unable to set FPSCR to KVM: %s"
8 kvm_failed_vscr_set(const char *msg) "Unable to set VSCR to KVM: %s"
9 kvm_failed_vr_set(int vr, const char *msg) "Unable to set VR%d to KVM: %s"
10 kvm_failed_fpscr_get(const char *msg) "Unable to get FPSCR from KVM: %s"
12 kvm_failed_vscr_get(const char *msg) "Unable to get VSCR from KVM: %s"
13 kvm_failed_vr_get(int vr, const char *msg) "Unable to get VR%d from KVM: %s"
17 kvm_failed_vpa_addr_set(const char *msg) "Unable to set VPA address to KVM: %s"
18 kvm_failed_slb_set(const char *msg) "Unable to set SLB shadow state to KVM: %s"
21 kvm_failed_put_vpa(void) "Warning: Unable to set VPA information to KVM"
[all …]
/openbmc/qemu/target/loongarch/
H A Dtrace-events4 kvm_failed_get_regs_core(const char *msg) "Failed to get core regs from KVM: %s"
5 kvm_failed_put_regs_core(const char *msg) "Failed to put core regs into KVM: %s"
6 kvm_failed_get_fpu(const char *msg) "Failed to get fpu from KVM: %s"
7 kvm_failed_put_fpu(const char *msg) "Failed to put fpu into KVM: %s"
8 kvm_failed_get_mpstate(const char *msg) "Failed to get mp_state from KVM: %s"
9 kvm_failed_put_mpstate(const char *msg) "Failed to put mp_state into KVM: %s"
10 kvm_failed_get_counter(const char *msg) "Failed to get counter from KVM: %s"
11 kvm_failed_put_counter(const char *msg) "Failed to put counter into KVM: %s"
12 kvm_failed_get_cpucfg(const char *msg) "Failed to get cpucfg from KVM: %s"
13 kvm_failed_put_cpucfg(const char *msg) "Failed to put cpucfg into KVM: %s"
/openbmc/linux/arch/x86/kvm/
H A DKconfig3 # KVM configuration
21 config KVM config
67 bool "Compile KVM with -Werror"
72 depends on KVM
76 Add -Werror to the build flags for KVM.
82 depends on KVM && IA32_FEAT_CTL
103 tristate "KVM for AMD processors support"
124 depends on KVM
134 depends on KVM
142 bool "Prove KVM MMU correctness"
[all …]
/openbmc/qemu/docs/specs/
H A Dppc-spapr-xive.rst52 KVM negotiation
73 XIVE support in KVM
77 kernels with XIVE KVM support are the following:
85 dual (default) XIVE KVM XIVE emul. XIVE KVM
86 xive XIVE KVM XIVE emul. XIVE KVM
87 xics XICS KVM XICS emul. XICS KVM
99 dual (default) XICS KVM XICS emul. XICS KVM
101 xics XICS KVM XICS emul. XICS KVM
109 No XIVE support in KVM
123 xics XICS KVM XICS emul. XICS KVM
[all …]
/openbmc/linux/Documentation/process/
H A Dmaintainer-kvm-x86.rst3 KVM x86
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
52 directly to the main KVM tree, i.e. do not route through the KVM x86 tree.
55 requests (from KVM x86 to main KVM) are sent for each KVM x86 topic branch,
113 non-KVM x86 files, i.e. draw the attention of KVM *and* tip tree maintainers.
250 Running KVM selftests and KVM-unit-tests is also mandatory (and stating the
352 tests that fail due to KVM bugs should be ordered after the KVM fixes.
357 KVM patches, first post the KVM changes and then provide a lore Link: to the
[all …]
/openbmc/linux/Documentation/arch/s390/
H A Dvfio-ap-locking.rst35 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
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
88 It is not necessary to take the Guests Lock to access the KVM pointer if the
[all …]
/openbmc/linux/Documentation/virt/kvm/x86/
H A Drunning-nested-guests.rst4 Running nested guests with KVM
9 example is a KVM guest that in turn runs on a KVM guest (the rest of
20 | KVM (/dev/kvm) |
31 - L0 – level-0; the bare metal host, running KVM
34 hypervisor", as it itself is capable of running KVM.
89 the KVM modules::
107 4. Unload and re-load the KVM Intel module::
159 nested guest with accelerated KVM.
184 Live migration with nested KVM
225 - Ensure you are actually running KVM on KVM. Sometimes people do not
[all …]
H A Derrata.rst7 Whenever perfect emulation of a CPU feature is impossible or too hard, KVM
11 This file documents some of the known limitations that KVM has in
43 When KVM_X2APIC_API_USE_32BIT_IDS is enabled, KVM activates a hack/quirk that
47 have the same physical APIC ID, KVM will deliver events targeting that APIC ID
49 not enabled, KVM follows x86 architecture when processing interrupts (all vCPUs
/openbmc/linux/Documentation/virt/kvm/s390/
H A Ds390-diag.rst4 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 …]
H A Ds390-pv.rst9 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;
106 The notification type intercepts inform KVM about guest environment
[all …]
/openbmc/linux/Documentation/virt/kvm/arm/
H A Dhypercalls.rst7 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
46 KVM does not offer
68 unknown. KVM does not offer firmware support for the workaround.
94 Note that KVM will not allow the userspace to configure the registers
[all …]
/openbmc/linux/arch/s390/kvm/
H A DKconfig3 # KVM configuration
9 prompt "KVM"
19 config KVM config
21 prompt "Kernel-based Virtual Machine (KVM) support"
52 depends on KVM
54 Allow CAP_SYS_ADMIN users to create KVM virtual machines that are
/openbmc/qemu/docs/system/ppc/
H A Dpseries.rst148 Switching between the KVM-PR and KVM-HV kernel module
155 If a host supports both KVM modes, and both KVM kernel modules are loaded, it is
163 KVM-PR
180 As KVM-PR can be run inside a pSeries guest, it can also provide nested
183 It is important to notice that, as KVM-HV provides a much better execution
185 years. Maintenance for KVM-PR has been minimal.
190 KVM-HV
202 pSeries guests as well, making nested virtualization possible with KVM-HV.
217 run. As long as you are in a supported environment, you can run KVM-PR or KVM-HV
221 | Platform | Host type | Bits | Page table format | KVM-HV | KVM-PR |
[all …]
/openbmc/linux/arch/powerpc/kvm/
H A DKconfig3 # KVM configuration
20 config KVM config
51 tristate "KVM support for PowerPC book3s_32 processors"
54 select KVM
71 select KVM
192 bool "KVM support for PowerPC E500v2 processors"
195 select KVM
211 select KVM
225 bool "KVM in-kernel MPIC emulation"
226 depends on KVM && PPC_E500
[all …]
/openbmc/linux/arch/arm64/kvm/
H A DKconfig3 # KVM configuration
21 menuconfig KVM config
22 bool "Kernel-based Virtual Machine (KVM) support"
53 depends on KVM
55 Say Y here to enable the debug mode for the non-VHE KVM EL2 object.
62 bool "Protected KVM hypervisor stacktraces"
/openbmc/qemu/docs/system/i386/
H A Dkvm-pv.rst1 Paravirtualized KVM features
7 In some cases when implementing hardware interfaces in software is slow, ``KVM``
13 Paravirtualized ``KVM`` features are represented as CPU flags. The following
14 features are enabled by default for any CPU model when ``KVM`` acceleration is
28 paravirtualized ``KVM`` features to the guest.
34 Expose a ``KVM`` specific paravirtualized clocksource to the guest. Supported
46 Note: since Linux v5.10 the feature is deprecated and not enabled by ``KVM``.
92 Note, by default, ``KVM`` allows the guest to use all currently supported
/openbmc/qemu/target/s390x/kvm/
H A Dtrace-events6 …_index, uint8_t state, const char *msg) "Warning: Unable to set cpu %d state %" PRIu8 " to KVM: %s"
9 kvm_sw_breakpoint(uint32_t n) "KVM: will use %d-byte sw breakpoints"
10 kvm_insn_unhandled_priv(uint32_t x) "KVM: unhandled PRIV: 0x%x"
11 kvm_insn_diag(uint32_t x) "KVM: unknown DIAG: 0x%x"
/openbmc/linux/Documentation/virt/kvm/devices/
H A Dvfio.rst15 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.
/openbmc/linux/arch/mips/kvm/
H A DKconfig3 # KVM configuration
18 config KVM config
19 tristate "Kernel-based Virtual Machine (KVM) support"
36 depends on KVM
/openbmc/linux/Documentation/translations/zh_CN/mm/
H A Dhwpoison.rst45 现在主要目标是KVM客户机，但它适用于所有类型的应用程序。支持KVM需要最近的qemu-kvm
48 对于KVM的使用，需要一个新的信号类型，这样KVM就可以用适当的地址将机器检查注入到客户
62 应用程序以温和的方式处理内存错误（例如，放弃受影响的对象） 这是KVM qemu使用的
/openbmc/linux/Documentation/admin-guide/hw-vuln/
H A Dmultihit.rst81 * - KVM: Mitigation: Split huge pages
83 * - KVM: Mitigation: VMX unsupported
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
125 The KVM hypervisor mitigation mechanism for marking huge pages as
[all …]
/openbmc/qemu/docs/system/arm/
H A Dcpu-features.rst27 when using the KVM accelerator and when running on a host CPU type that
28 supports the feature. While ``aarch64`` currently only works with KVM,
29 it could work with TCG. CPU features that are specific to KVM are
30 prefixed with "kvm-" and are described in "KVM VCPU Features".
58 all SVE vector lengths can be supported, when KVM is in use it's more
122 A note about CPU models and KVM
170 KVM VCPU Features
173 KVM VCPU features are CPU features that are specific to KVM, such as
178 the list of KVM VCPU features and their descriptions.
198 Since v5.2, kvm-steal-time is enabled by default when KVM is
[all …]
/openbmc/linux/Documentation/translations/zh_CN/arch/arm64/
H A Dperf.rst54 这些属性分别排除了 KVM 宿主机和客户机。
56 KVM 宿主机可能运行在 EL0（用户空间），EL1（non-VHE 内核）和
59 KVM 客户机可能运行在 EL0（用户空间）和 EL1（内核）。
/openbmc/linux/Documentation/translations/zh_TW/arch/arm64/
H A Dperf.rst55 這些屬性分別排除了 KVM 宿主機和客戶機。
57 KVM 宿主機可能運行在 EL0（用戶空間），EL1（non-VHE 內核）和
60 KVM 客戶機可能運行在 EL0（用戶空間）和 EL1（內核）。

12345678910