Home
last modified time | relevance | path

Searched full:hypervisors (Results 1 – 25 of 81) sorted by relevance

1234

/kernel/linux/linux-4.19/Documentation/virtual/
Dparavirt_ops.txt6 different hypervisors, this restriction was removed with pv_ops.
8 hypervisors. It allows each hypervisor to override critical operations and
10 including native machine -- without any hypervisors.
D00-INDEX7 - Describes the Linux kernel pv_ops to support different hypervisors
/kernel/linux/linux-5.10/arch/x86/kernel/cpu/
Dhypervisor.c29 static const __initconst struct hypervisor_x86 * const hypervisors[] = variable
67 for (p = hypervisors; p < hypervisors + ARRAY_SIZE(hypervisors); p++) { in detect_hypervisor_vendor()
/kernel/linux/linux-4.19/arch/x86/kernel/cpu/
Dhypervisor.c36 static const __initconst struct hypervisor_x86 * const hypervisors[] = variable
63 for (p = hypervisors; p < hypervisors + ARRAY_SIZE(hypervisors); p++) { in detect_hypervisor_vendor()
/kernel/linux/linux-5.10/Documentation/virt/
Dparavirt_ops.rst9 different hypervisors, this restriction was removed with pv_ops.
11 hypervisors. It allows each hypervisor to override critical operations and
13 including native machine -- without any hypervisors.
/kernel/linux/linux-4.19/Documentation/virtual/kvm/
Dnested-vmx.txt9 *cannot* themselves be hypervisors running their own guests, because in VMX,
13 hypervisors (which use VMX) with their own nested guests. It does so by
58 which are used in practice by popular hypervisors (KVM and others).
Ds390-diag.txt6 hypervisors.
32 documentation for the s390 hypervisors defining them.
/kernel/linux/linux-5.10/Documentation/virt/kvm/
Dnested-vmx.rst12 *cannot* themselves be hypervisors running their own guests, because in VMX,
16 hypervisors (which use VMX) with their own nested guests. It does so by
61 which are used in practice by popular hypervisors (KVM and others).
Ds390-diag.rst9 hypervisors.
35 documentation for the s390 hypervisors defining them.
/kernel/linux/linux-5.10/tools/testing/selftests/net/
Dtest_vxlan_under_vrf.sh6 # It simulates two hypervisors running a VM each using four network namespaces:
8 # A small VXLAN tunnel is made between the two hypervisors to have the two vms
64 # Setup "Hypervisors" simulated with netns
/kernel/linux/linux-5.10/tools/testing/selftests/powerpc/vphn/asm/
Dlppaca.h34 * These definitions relate to hypervisors that only exist when using
57 * Pre-v4.14 KVM hypervisors reject the VPA if its size field is smaller than
/kernel/linux/linux-5.10/arch/powerpc/include/asm/
Dlppaca.h34 * These definitions relate to hypervisors that only exist when using
57 * Pre-v4.14 KVM hypervisors reject the VPA if its size field is smaller than
/kernel/linux/linux-5.10/drivers/input/mouse/
Dvmmouse.h3 * Driver for Virtual PS/2 Mouse on VMware and QEMU hypervisors.
/kernel/linux/linux-4.19/arch/powerpc/include/asm/
Dlppaca.h24 * These definitions relate to hypervisors that only exist when using
47 * Pre-v4.14 KVM hypervisors reject the VPA if its size field is smaller than
/kernel/linux/linux-4.19/drivers/input/mouse/
Dvmmouse.h2 * Driver for Virtual PS/2 Mouse on VMware and QEMU hypervisors.
/kernel/linux/linux-5.10/include/xen/interface/
Delfnote.h186 * kernel to specify support for features that older hypervisors don't
187 * know about. The set of features 4.2 and newer hypervisors will
/kernel/linux/linux-4.19/include/xen/interface/
Delfnote.h186 * kernel to specify support for features that older hypervisors don't
187 * know about. The set of features 4.2 and newer hypervisors will
/kernel/linux/linux-4.19/arch/x86/include/asm/
Dtlb.h21 * shootdown, enablement code for several hypervisors overrides
Dqspinlock.h80 * On hypervisors without PARAVIRT_SPINLOCKS support we fall in virt_spin_lock()
/kernel/linux/linux-5.10/arch/x86/include/asm/
Dtlb.h29 * shootdown, enablement code for several hypervisors overrides
/kernel/linux/linux-4.19/Documentation/virtual/kvm/arm/
Dhyp-abi.txt28 Linux hypervisors.
/kernel/linux/linux-4.19/Documentation/admin-guide/hw-vuln/
Dl1tf.rst373 the hypervisors, i.e. unconditional L1D flushing
376 is still possible after boot. Hypervisors will issue a
389 is still possible after boot. Hypervisors will issue a
398 is still possible after boot. Hypervisors will issue a
403 flush,nowarn Same as 'flush', but hypervisors will not warn when a VM is
/kernel/linux/linux-5.10/Documentation/admin-guide/hw-vuln/
Dl1tf.rst373 the hypervisors, i.e. unconditional L1D flushing
376 is still possible after boot. Hypervisors will issue a
389 is still possible after boot. Hypervisors will issue a
398 is still possible after boot. Hypervisors will issue a
403 flush,nowarn Same as 'flush', but hypervisors will not warn when a VM is
/kernel/linux/linux-4.19/drivers/tty/hvc/
DKconfig7 hypervisors (pSeries, iSeries, Xen).
/kernel/linux/linux-5.10/drivers/tty/hvc/
DKconfig7 hypervisors (pSeries, iSeries, Xen).

1234