Home
last modified time | relevance | path

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

12345678910

/linux/Documentation/ABI/stable/
A Dsysfs-hypervisor-xen1 What: /sys/hypervisor/compilation/compile_date
8 in the hypervisor.
17 in the hypervisor.
26 in the hypervisor.
57 in the hypervisor.
74 in the hypervisor.
83 What: /sys/hypervisor/type
88 Type of hypervisor:
89 "xen": Xen hypervisor
91 What: /sys/hypervisor/uuid
[all …]
/linux/Documentation/ABI/testing/
A 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.
/linux/Documentation/virt/kvm/arm/
A 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.
70 Any other value of r0/x0 triggers a hypervisor-specific handling,
A Dpvtime.rst12 some hypervisor service calls to support a paravirtualized guest obtaining a
31 PV-time feature is supported by the hypervisor.
45 meaningfully filled by the hypervisor (see structure below).
70 The structure will be updated by the hypervisor prior to scheduling a VCPU. It
/linux/Documentation/misc-devices/
A 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,
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
152 RDMA of the HMC ID to the hypervisor, and then sends an Interface Open
156 connection. Finally, the hypervisor sends an Interface Open Response
177 During normal runtime, the management application and the hypervisor
179 sending data to the hypervisor, the management application performs a
[all …]
/linux/arch/arm/boot/dts/
A 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/Documentation/virt/acrn/
A 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.
A 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/Documentation/powerpc/
A 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 priviledged [3]_ or for other services managed by the
26 hypervisor.
30 guest issues a with necessary input operands. The hypervisor after performing
43 Once control returns back to the guest after hypervisor has serviced the
134 initial call and use the hypervisor returned value of *continue-token*
135 for each subsequent hcall until hypervisor returns a non *H_CONTINUE*
[all …]
/linux/Documentation/devicetree/bindings/arm/
A Dxen.txt1 * Xen hypervisor device tree bindings
3 Xen ARM virtual platforms shall have a top-level "hypervisor" node with
21 under /hypervisor with following parameters:
43 hypervisor {
58 they differ because they are provided by the Xen hypervisor, together with a set
/linux/Documentation/virt/kvm/
A Drunning-nested-guests.rst6 can be KVM-based or a different hypervisor). The straightforward
32 hypervisor", as it itself is capable of running KVM.
41 hypervisor running on bare metal, adding another layer and
43 metal, running the LPAR hypervisor), L1 (host hypervisor), L2
44 (guest hypervisor), L3 (nested guest).
60 hypervisor" (level-1 guest). This in turn allows you to create
156 then the guest hypervisor will subsequently be capable of running a
163 1. On the host hypervisor (L0), enable the ``nested`` parameter on
173 2. The guest hypervisor (L1) must be provided with the ``sie`` CPU
177 3. Now the KVM module can be loaded in the L1 (guest hypervisor)::
[all …]
A 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
305 the hypervisor doesn't support this field.
318 written to by the hypervisor, typically at the time of interrupt
322 later be polled by the hypervisor.
331 primitives to synchronise with the hypervisor.
333 However, hypervisor can set and clear this memory bit at any time:
334 therefore to make sure hypervisor does not interrupt the
[all …]
A Damd-memory-encryption.rst11 virtual machines (VMs) under the control of a hypervisor. When enabled,
15 The hypervisor can determine the SEV support through the CPUID
52 key management interface to perform common hypervisor activities such as
85 The KVM_SEV_INIT command is used by the hypervisor to initialize the SEV platform
209 The KVM_SEV_DEBUG_DECRYPT command can be used by the hypervisor to request the
229 The KVM_SEV_DEBUG_ENCRYPT command can be used by the hypervisor to request the
249 The KVM_SEV_LAUNCH_SECRET command can be used by the hypervisor to inject secret
296 The KVM_SEV_SEND_START command can be used by the hypervisor to create an
356 issued by the hypervisor to delete the encryption context.
401 The KVM_SEV_RECEIVE_UPDATE_DATA command can be used by the hypervisor to copy
[all …]
A 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/Documentation/devicetree/bindings/powerpc/fsl/
A 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/drivers/virt/
A DKconfig17 tristate "Freescale hypervisor management driver"
21 The Freescale hypervisor management driver provides several services
22 to drivers and applications related to the Freescale hypervisor:
/linux/arch/powerpc/kvm/
A DKconfig83 tristate "KVM for POWER7 and later using hypervisor mode in host"
91 hypervisor mode available to the host.
104 tristate "KVM support without using hypervisor mode in host"
109 without using hypervisor mode in the host, by running the
113 This is not as fast as using hypervisor mode, but works on
114 machines where hypervisor mode is not available or not usable,
120 bool "Detailed timing for hypervisor real-mode code"
/linux/Documentation/admin-guide/hw-vuln/
A 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.
353 managed and sanitized by the hypervisor. Though disabling EPT has a
385 flush Leaves SMT enabled and enables the default hypervisor
406 off Disables hypervisor mitigations and doesn't emit any
409 on both hypervisor and bare metal.
421 The KVM hypervisor mitigation mechanism, flushing the L1D cache when
550 EPT can be disabled in the hypervisor via the 'kvm-intel.ept'
557 the bare metal hypervisor, the nested hypervisor and the nested virtual
[all …]
/linux/arch/sparc/mm/
A 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/Documentation/networking/
A 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
79 net_failover also enables hypervisor controlled live migration to be supported
84 the source hypervisor.
/linux/arch/sparc/kernel/
A 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()
A Dsmp_64.c110 if (tlb_type == hypervisor) in smp_callin()
362 if (tlb_type == hypervisor) { in smp_boot_one_cpu()
941 if (tlb_type == hypervisor) in smp_flush_dcache_page_impl()
982 if (tlb_type == hypervisor) in flush_dcache_page_all()
1027 if (tlb_type == hypervisor && in smp_fetch_global_pmu()
1291 if (tlb_type != hypervisor) in __cpu_up()
1306 if (tlb_type == hypervisor) { in cpu_play_dead()
1470 if (tlb_type != hypervisor) in smp_init_cpu_poke()
1504 if (tlb_type == hypervisor) { in smp_send_stop()
1667 if (tlb_type == hypervisor) in setup_per_cpu_areas()
/linux/Documentation/arm64/
A Dperf.rst38 This attribute excludes the hypervisor.
41 be the hypervisor.
44 hypervisor to be any code that runs at EL2 which is predominantly used for
57 kernel or non-VHE hypervisor).
/linux/net/vmw_vsock/
A DKconfig10 allowing communication between Virtual Machines and hypervisor
13 You should also select one or more hypervisor-specific transports
48 hypervisor.
/linux/drivers/xen/
A DKconfig105 information with each other and with the hypervisor.
123 bool "Create xen entries under /sys/hypervisor"
128 Create entries under /sys/hypervisor describing the Xen
129 hypervisor environment. When running native or in another
130 virtual environment, /sys/hypervisor will still be present,
278 hypervisor.
281 said information to the Xen hypervisor. Then the Xen hypervisor can
319 Exports hypervisor symbols (along with their types and addresses) via

Completed in 44 milliseconds

12345678910