Searched full:hypervisor (Results 1 – 25 of 122) sorted by relevance
12345
| /Documentation/ABI/stable/ |
| D | sysfs-hypervisor-xen | 1 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 …]
|
| /Documentation/arch/powerpc/ |
| D | ultravisor.rst | 32 | Hypervisor |
37 PEF protects SVMs from the hypervisor, privileged users, and other
40 hypervisor services. The Ultravisor filters calls between the SVMs
41 and the hypervisor to assure that information does not accidentally
42 leak. All hypercalls except H_RANDOM are reflected to the hypervisor.
43 H_RANDOM is not reflected to prevent the hypervisor from influencing
47 in the CPU. Some of the resources which were previously hypervisor
61 * HRFID cannot be used to set the MSR(S) bit. If the hypervisor needs
96 | 0 | 1 | 0 | Hypervisor |
105 access secure memory. This means that the Hypervisor cannot access
[all …]
|
| D | papr_hcalls.rst | 12 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
37 is covered in section 14.5.3 of ref [2]_. Switch to the Hypervisor context is
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-hypervisor-xen | 1 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.
|
| D | sysfs-secvar | 68 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
|
| /Documentation/virt/kvm/arm/ |
| D | hyp-abi.rst | 8 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,
|
| D | pkvm.rst | 16 The major implementation change brought about by pKVM is that the hypervisor
22 at stage-2, providing the hypervisor code with a mechanism to restrict host
28 The pKVM hypervisor is enabled by booting the host kernel at EL2 with
30 in either protected or non-protected state, although the hypervisor is still
61 Since the host is unable to tear down the hypervisor when pKVM is enabled,
91 injection of an abort at EL1 by the hypervisor. For accesses originating from
|
| /Documentation/virt/gunyah/ |
| D | index.rst | 4 Gunyah Hypervisor
12 Gunyah is a Type-1 hypervisor which is independent of any OS kernel, and runs in
16 hypervisor.
18 Gunyah is an open source hypervisor. The source repository is available at
19 https://github.com/quic/gunyah-hypervisor.
29 1. Hypervisor vCPU scheduling in which Gunyah hypervisor schedules vCPUS on
58 directly provided by the hypervisor as well as core virtual platform devices
66 hypervisor style on-demand paging and/or device emulation.
75 Services/resources provided by the Gunyah hypervisor are accessible to a
78 hypervisor object (conceptually similar to a file-descriptor).
[all …]
|
| D | message-queue.rst | 7 message queue is unidirectional and buffered in the hypervisor. A full-duplex
23 with the message to request the hypervisor to add the message to
24 message queue 1's queue. The hypervisor copies memory into the internal
53 | VM_A | |Gunyah hypervisor| | VM_B |
|
| /Documentation/virt/acrn/ |
| D | introduction.rst | 3 ACRN Hypervisor Introduction
6 The ACRN Hypervisor is a Type 1 hypervisor, running directly on bare-metal
11 devices for a User VM based on command line configurations. ACRN Hypervisor
13 hypervisor services to the ACRN userspace.
30 | ACRN Hypervisor |
38 ioctls to communicate with the HSM. HSM implements hypervisor services by
39 interacting with the ACRN Hypervisor via hypercalls. HSM exports a char device
42 The ACRN hypervisor is open for contribution from anyone. The source repo is
43 available at https://github.com/projectacrn/acrn-hypervisor.
|
| D | io-request.rst | 6 An I/O request of a User VM, which is constructed by the hypervisor, is
7 distributed by the ACRN Hypervisor Service Module to an I/O client
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
63 | | I/O handler | ACRN Hypervisor |
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
|
| /Documentation/misc-devices/ |
| D | ibmvmc.rst | 24 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 …]
|
| /Documentation/virt/geniezone/ |
| D | introduction.rst | 9 GenieZone hypervisor (gzvm) is a type-I hypervisor that supports various virtual
13 hypervisor can be booted independently, it requires the assistance of GenieZone
14 hypervisor kernel driver (also named gzvm) to leverage the ability of Linux
34 dictated to the privilege models managed by GenieZone hypervisor for security
35 reason. With the help of the gzvm module, the hypervisor is able to manipulate
40 The gzvm hypervisor emulates a virtual mobile platform for guest OS running on
59 hypervisor with the help of gzvm module, both virtual and physical ones.
86 interrupts, the GenieZone hypervisor writes to list registers and triggers
|
| /Documentation/devicetree/bindings/firmware/ |
| D | mediatek,geniezone.yaml | 7 title: MediaTek GenieZone hypervisor
13 GenieZone is a proprietary type-I hypervisor firmware developed by MediaTek,
18 exposes hypervisor control interfaces to the VMM for managing virtual
32 hypervisor {
|
| D | gunyah-hypervisor.yaml | 4 $id: http://devicetree.org/schemas/firmware/gunyah-hypervisor.yaml#
7 title: Gunyah Hypervisor
20 const: gunyah-hypervisor
70 hypervisor {
73 compatible = "gunyah-hypervisor";
|
| /Documentation/virt/kvm/x86/ |
| D | msr.rst | 34 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
223 to by the hypervisor at the time of injection. Only first bit of 'flags'
235 hypervisor at the time of APF 'page ready' event injection. The content
276 whose data will be filled in by the hypervisor periodically. Only one
279 The hypervisor may update this structure at any time it sees fit until
304 the hypervisor doesn't support this field.
317 written to by the hypervisor, typically at the time of interrupt
[all …]
|
| D | running-nested-guests.rst | 8 can be KVM-based or a different hypervisor). The straightforward
19 | L1 (Guest Hypervisor) |
23 | L0 (Host Hypervisor) |
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
[all …]
|
| /Documentation/arch/x86/ |
| D | tdx.rst | 199 normal functionality of a hypervisor must be moved into the guest. This is
202 require the hypervisor to be consulted.
205 guest to the hypervisor or the TDX module.
252 The #VE MSRs are typically able to be handled by the hypervisor. Guests
253 can make a hypercall to the hypervisor to handle the #VE.
265 hypervisor. For such cases, the Intel TDX module architecture defines two
268 - Bit fields for which the hypervisor controls the value seen by the guest
271 - Bit fields for which the hypervisor configures the value such that the
273 fields, the hypervisor can mask off the native values, but it can not
277 not know how to handle. The guest kernel may ask the hypervisor for the
[all …]
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | msi-pic.txt | 37 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
|
| /Documentation/virt/coco/ |
| D | sev-guest.rst | 10 The SEV API is a set of ioctls that are used by the guest or hypervisor
14 - Hypervisor ioctls: These query and set global attributes which affect the
30 hypervisor or guest. The ioctl can be used inside the guest or the
31 hypervisor.
131 The certificate data returned is being provided by the hypervisor through the
147 :Type: hypervisor ioctl cmd
158 :Type: hypervisor ioctl cmd
169 :Type: hypervisor ioctl cmd
182 :Type: hypervisor ioctl cmd
210 being generated due to changes in validation state if the hypervisor tries
[all …]
|
| /Documentation/admin-guide/hw-vuln/ |
| D | l1tf.rst | 104 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 …]
|
| /Documentation/driver-api/virtio/ |
| D | virtio.rst | 15 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
|
| /Documentation/networking/ |
| D | net_failover.rst | 24 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
136 # Source Hypervisor migrate.sh
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
|
| /Documentation/devicetree/bindings/arm/ |
| D | xen.txt | 1 * 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
|
| /Documentation/virt/kvm/ |
| D | ppc-pv.rst | 12 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
|
12345