Home
last modified time | relevance | path

Searched refs:hypervisor (Results 1 – 25 of 167) sorted by relevance

1234567

/linux-6.6.21/Documentation/ABI/stable/
Dsysfs-hypervisor-xen1 What: /sys/hypervisor/compilation/compile_date
6 Contains the build time stamp of the Xen hypervisor
8 in the hypervisor.
10 What: /sys/hypervisor/compilation/compiled_by
15 Contains information who built the Xen hypervisor
17 in the hypervisor.
19 What: /sys/hypervisor/compilation/compiler
24 Compiler which was used to build the Xen hypervisor
26 in the hypervisor.
28 What: /sys/hypervisor/properties/capabilities
[all …]
/linux-6.6.21/Documentation/ABI/testing/
Dsysfs-hypervisor-xen1 What: /sys/hypervisor/guest_type
12 What: /sys/hypervisor/pmu/pmu_mode
24 privileged (e.g. dom0), the hypervisor
25 "all" The guest can profile itself, the hypervisor
30 What: /sys/hypervisor/pmu/pmu_features
39 What: /sys/hypervisor/properties/buildid
44 Build id of the hypervisor, needed for hypervisor live patching.
46 in the hypervisor.
Dsysfs-secvar68 Description: Config version as reported by the hypervisor in ASCII decimal
105 Description: Bitmask of supported policy flags by the hypervisor,
107 hypervisor documentation for what these flags are.
114 Description: Bitmask of flags indicating which algorithms the hypervisor
116 hexadecimal ASCII string. Consult the hypervisor documentation
/linux-6.6.21/Documentation/virt/kvm/arm/
Dhyp-abi.rst8 hypervisor layer when running Linux as a hypervisor (for example
10 hypervisor when running as a guest (under Xen, KVM or any other
11 hypervisor), or any hypervisor-specific interaction when the kernel is
16 booted at HYP. It can also be used by a hypervisor other than KVM
19 On arm and arm64 (without VHE), the kernel doesn't run in hypervisor
21 hypervisor to be either installed or torn down.
28 Unless specified otherwise, any built-in hypervisor must implement
36 Set HVBAR/VBAR_EL2 to 'vectors' to enable a hypervisor. 'vectors'
47 hypervisor.
71 Any other value of r0/x0 triggers a hypervisor-specific handling,
Dpvtime.rst12 some hypervisor service calls to support a paravirtualized guest obtaining a
32 PV-time feature is supported by the hypervisor.
47 meaningfully filled by the hypervisor (see structure below).
72 The structure will be updated by the hypervisor prior to scheduling a VCPU. It
/linux-6.6.21/Documentation/misc-devices/
Dibmvmc.rst24 interface between the hypervisor and a management partition. This interface
47 application using a combination of HMC to hypervisor interfaces and
50 The set of HMC to hypervisor messages supported by the management
51 application component are passed to the hypervisor over a VMC interface,
68 for communicating between the management application and the hypervisor. It
75 defined that must take place to establish that both the hypervisor and
80 when the hypervisor detects one of the peer partitions has abnormally
86 the hypervisor. As most HMC messages far exceed the size of a CRQ buffer,
102 from the hypervisor to partition are also reported in this queue.
119 resources available in both the management partition and the hypervisor.
[all …]
/linux-6.6.21/arch/arm/boot/dts/xen/
Dxenvm-4.2.dts20 /* this field is going to be adjusted by the hypervisor */
50 /* this field is going to be adjusted by the hypervisor */
71 hypervisor {
73 /* this field is going to be adjusted by the hypervisor */
75 /* this field is going to be adjusted by the hypervisor */
/linux-6.6.21/Documentation/virt/acrn/
Dintroduction.rst6 The ACRN Hypervisor is a Type 1 hypervisor, running directly on bare-metal
13 hypervisor services to the ACRN userspace.
38 ioctls to communicate with the HSM. HSM implements hypervisor services by
42 The ACRN hypervisor is open for contribution from anyone. The source repo is
43 available at https://github.com/projectacrn/acrn-hypervisor.
Dio-request.rst6 An I/O request of a User VM, which is constructed by the hypervisor, is
15 communication between the hypervisor and Service VM. An I/O request is a
17 an I/O handler of the hypervisor when a trapped I/O access happens in a User
19 the GPA (Guest Physical Address) of the buffer to the hypervisor. The buffer is
81 An I/O request in COMPLETE or FREE state is owned by the hypervisor. HSM and
87 a. The I/O handler of the hypervisor will fill an I/O request with PENDING
89 b. The hypervisor makes an upcall, which is a notification interrupt, to
96 f. The HSM updates I/O requests states to COMPLETE and notifies the hypervisor
/linux-6.6.21/Documentation/arch/x86/
Dtdx.rst14 normal functionality of a hypervisor must be moved into the guest. This is
17 require the hypervisor to be consulted.
20 guest to the hypervisor or the TDX module.
67 The #VE MSRs are typically able to be handled by the hypervisor. Guests
68 can make a hypercall to the hypervisor to handle the #VE.
80 hypervisor. For such cases, the Intel TDX module architecture defines two
83 - Bit fields for which the hypervisor controls the value seen by the guest
86 - Bit fields for which the hypervisor configures the value such that the
88 fields, the hypervisor can mask off the native values, but it can not
92 not know how to handle. The guest kernel may ask the hypervisor for the
[all …]
/linux-6.6.21/Documentation/powerpc/
Dpapr_hcalls.rst12 operating system and how it should interact with the hypervisor for
15 - **IBM PowerVM (PHYP)**: IBM's proprietary hypervisor that supports AIX,
22 On PPC64 arch a guest kernel running on top of a PAPR hypervisor is called
24 issue hypercalls to the hypervisor whenever it needs to perform an action
25 that is hypervisor privileged [3]_ or for other services managed by the
26 hypervisor.
29 asking hypervisor to perform a privileged operation on behalf of the guest. The
30 guest issues a with necessary input operands. The hypervisor after performing
36 The ABI specification for a hcall between a pseries guest and PAPR hypervisor
43 Once control returns back to the guest after hypervisor has serviced the
[all …]
/linux-6.6.21/Documentation/devicetree/bindings/arm/
Dxen.txt1 * Xen hypervisor device tree bindings
3 Xen ARM virtual platforms shall have a top-level "hypervisor" node with
23 under /hypervisor with following parameters:
45 hypervisor {
60 they differ because they are provided by the Xen hypervisor, together with a set
/linux-6.6.21/drivers/virt/
DKconfig21 Say Y here to use the hypervisor-provided Virtual Machine Generation ID
28 tristate "Freescale hypervisor management driver"
32 The Freescale hypervisor management driver provides several services
33 to drivers and applications related to the Freescale hypervisor:
/linux-6.6.21/arch/arm64/kvm/
DKconfig56 Failure reports will BUG() in the hypervisor. This is intended for
57 local EL2 hypervisor development.
62 bool "Protected KVM hypervisor stacktraces"
66 Say Y here to enable pKVM hypervisor stacktraces on hyp_panic()
/linux-6.6.21/Documentation/devicetree/bindings/powerpc/fsl/
Dmsi-pic.txt37 This property may be used in virtualized environments where the hypervisor
81 The Freescale hypervisor and msi-address-64
87 In a virtualized environment, the hypervisor may need to create an IOMMU
88 mapping for MSIIR. The Freescale ePAPR hypervisor has this requirement
90 (PAMU), which is currently the only IOMMU that the hypervisor supports.
106 Therefore, the hypervisor has to create a subwindow inside the same
110 address of MSIIR. The hypervisor configures the PAMU to map that address to
/linux-6.6.21/Documentation/virt/kvm/x86/
Drunning-nested-guests.rst8 can be KVM-based or a different hypervisor). The straightforward
34 hypervisor", as it itself is capable of running KVM.
43 hypervisor running on bare metal, adding another layer and
45 metal, running the LPAR hypervisor), L1 (host hypervisor), L2
46 (guest hypervisor), L3 (nested guest).
62 hypervisor" (level-1 guest). This in turn allows you to create
158 then the guest hypervisor will subsequently be capable of running a
165 1. On the host hypervisor (L0), enable the ``nested`` parameter on
175 2. The guest hypervisor (L1) must be provided with the ``sie`` CPU
179 3. Now the KVM module can be loaded in the L1 (guest hypervisor)::
[all …]
Dmsr.rst34 whose data will be filled in by the hypervisor. The hypervisor is only
78 whose data will be filled in by the hypervisor periodically. Only one
81 The hypervisor may update this structure at any time it sees fit until
127 coordinated between the guest and the hypervisor. Availability
224 to by the hypervisor at the time of injection. Only first bit of 'flags'
236 hypervisor at the time of APF 'page ready' event injection. The content
277 whose data will be filled in by the hypervisor periodically. Only one
280 The hypervisor may update this structure at any time it sees fit until
305 the hypervisor doesn't support this field.
318 written to by the hypervisor, typically at the time of interrupt
[all …]
Damd-memory-encryption.rst13 virtual machines (VMs) under the control of a hypervisor. When enabled,
17 The hypervisor can determine the SEV support through the CPUID
54 key management interface to perform common hypervisor activities such as
87 The KVM_SEV_INIT command is used by the hypervisor to initialize the SEV platform
216 The KVM_SEV_DEBUG_DECRYPT command can be used by the hypervisor to request the
236 The KVM_SEV_DEBUG_ENCRYPT command can be used by the hypervisor to request the
256 The KVM_SEV_LAUNCH_SECRET command can be used by the hypervisor to inject secret
272 __u64 trans_uaddr; /* the hypervisor memory region which contains the secret */
279 The KVM_SEV_GET_ATTESTATION_REPORT command can be used by the hypervisor to query the attestation
303 The KVM_SEV_SEND_START command can be used by the hypervisor to create an
[all …]
/linux-6.6.21/Documentation/admin-guide/hw-vuln/
Dl1tf.rst104 only possible, when the hypervisor does not sanitize the content of the
174 the hypervisor flushes the L1D before entering the guest.
195 address space layout of the hypervisor.
228 host OS (hypervisor) context and the other in guest context. The amount
353 managed and sanitized by the hypervisor. Though disabling EPT has a
357 EPT can be disabled in the hypervisor via the 'kvm-intel.ept' parameter.
385 flush Leaves SMT enabled and enables the default hypervisor
394 flush,nosmt Disables SMT and enables the default hypervisor mitigation,
406 off Disables hypervisor mitigations and doesn't emit any
409 on both hypervisor and bare metal.
[all …]
/linux-6.6.21/arch/sparc/mm/
Dtsb.c129 if (tlb_type == cheetah_plus || tlb_type == hypervisor) in flush_tsb_user()
143 if (tlb_type == cheetah_plus || tlb_type == hypervisor) in flush_tsb_user()
162 if (tlb_type == cheetah_plus || tlb_type == hypervisor) in flush_tsb_user_page()
177 if (tlb_type == cheetah_plus || tlb_type == hypervisor) in flush_tsb_user_page()
273 if (tlb_type == cheetah_plus || tlb_type == hypervisor) { in setup_tsb_params()
291 if (tlb_type == hypervisor) { in setup_tsb_params()
505 if (tlb_type == cheetah_plus || tlb_type == hypervisor) { in tsb_grow()
/linux-6.6.21/Documentation/virt/kvm/
Dppc-pv.rst12 instructions that needlessly return us to the hypervisor even though they
16 and transforms them into unprivileged ones with some help from the hypervisor.
25 Linux is running on KVM, a node /hypervisor exists. That node contains a
34 Inside the device tree's /hypervisor node there's a property called
73 To enable communication between the hypervisor and guest there is a new shared
127 The MSR contains bits that require hypervisor intervention and bits that do
128 not require direct hypervisor intervention because they only get interpreted
129 when entering the guest or don't have any impact on the hypervisor's behavior.
213 These are the same hypercalls that pHyp, the POWER hypervisor, implements. Some of
/linux-6.6.21/arch/sparc/kernel/
Dsetup_64.c178 if (tlb_type != hypervisor) { in per_cpu_patch()
200 case hypervisor: in per_cpu_patch()
282 if (tlb_type != hypervisor) in sun4v_patch()
538 else if (tlb_type == hypervisor) { in init_sparc64_elf_hwcap()
578 if (tlb_type == hypervisor) { in init_sparc64_elf_hwcap()
648 if (tlb_type == hypervisor) in setup_arch()
/linux-6.6.21/Documentation/driver-api/virtio/
Dvirtio.rst15 for paravirtualized devices implemented by a hypervisor, it can be used
20 devices provided by the hypervisor, which exposes them as virtio devices
28 hypervisor, they're exposed to the guest as if they are physical devices
35 the hypervisor is done through shared memory (that's what makes virtio
61 specifically, the trigger will be an interrupt issued by the hypervisor
78 the hypervisor defines it. Taking the `QEMU virtio-console
/linux-6.6.21/Documentation/networking/
Dnet_failover.rst24 datapath. It also enables hypervisor controlled live migration of a VM with
31 net_failover enables hypervisor controlled accelerated datapath to virtio-net
34 To support this, the hypervisor needs to enable VIRTIO_NET_F_STANDBY
116 net_failover also enables hypervisor controlled live migration to be supported
121 the source hypervisor. Note: It is assumed that the VM is connected to a
169 On the destination hypervisor, a shared bridge 'br0' is created before migration
173 The following script is executed on the destination hypervisor once migration
/linux-6.6.21/arch/powerpc/kvm/
DKconfig85 tristate "KVM for POWER7 and later using hypervisor mode in host"
93 hypervisor mode available to the host.
106 tristate "KVM support without using hypervisor mode in host"
112 without using hypervisor mode in the host, by running the
119 This is not as fast as using hypervisor mode, but works on
120 machines where hypervisor mode is not available or not usable,
148 bool "Detailed timing for hypervisor real-mode code (for POWER8)"

1234567