Searched full:hypervisor (Results 1 – 25 of 753) sorted by relevance
12345678910>>...31
| /Linux-v6.1/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 …]
|
| /Linux-v6.1/Documentation/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 priviledged [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 …]
|
| /Linux-v6.1/Documentation/x86/ |
| D | tdx.rst | 14 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-v6.1/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 …]
|
| /Linux-v6.1/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,
|
| /Linux-v6.1/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.
|
| /Linux-v6.1/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
|
| /Linux-v6.1/include/uapi/linux/ |
| D | acrn.h | 3 * Userspace interface for /dev/acrn_hsm - ACRN Hypervisor Service Module
90 * @completion_polling: Polling flag. Hypervisor will poll completion of the
106 * An I/O request in COMPLETE or FREE state is owned by the hypervisor. HSM and
116 * | hypervisor:
132 * | notifies the hypervisor
134 * | hypervisor:
137 * | hypervisor:
145 * Atomic and barriers are required when HSM and hypervisor accessing the state
185 * @vmid: User VM ID returned from the hypervisor
187 * @vcpu_num: Number of vCPU in the VM. Return from hypervisor.
[all …]
|
| D | fsl_hypervisor.h | 3 * Freescale hypervisor ioctl and kernel interface
36 * This file is used by the Freescale hypervisor management driver. It can
48 * @ret: return error code from the hypervisor
61 * @ret: return error code from the hypervisor
82 * @ret: return error code from the hypervisor
98 * @ret: return error code from the hypervisor
111 * @ret: return error code from the hypervisor
153 * @ret: return error code from the hypervisor
165 * @ret: return error code from the hypervisor
|
| /Linux-v6.1/drivers/tty/hvc/ |
| D | Kconfig | 6 Generic "hypervisor virtual console" infrastructure for various
15 bool "pSeries Hypervisor Virtual Console support"
20 pSeries machines when partitioned support a hypervisor virtual
45 bool "z/VM IUCV Hypervisor console support (VM only)"
51 This driver provides a Hypervisor console (HVC) back-end to access
55 bool "Xen Hypervisor Console support"
64 bool "Xen Hypervisor Multiple Consoles support"
72 bool "udbg based fake hypervisor console"
120 tristate "IBM Hypervisor Virtual Console Server support"
|
| /Linux-v6.1/arch/arm64/kvm/ |
| D | stacktrace.c | 3 * KVM nVHE hypervisor stack tracing support.
75 * The nVHE hypervisor stack is mapped in the flexible 'private' VA range, to
79 * The kernel VA is calculated as an offset from the kernel VA of the hypervisor
117 * The FP is in the hypervisor VA space. Convert it to the kernel VA in unwind_next()
143 * @arg : the hypervisor offset, used for address translation
171 * @hyp_offset: hypervisor offset, used for address translation.
175 * the need for shared buffers between host and hypervisor for
206 * @hyp_offset: hypervisor offset, used for address translation.
210 * host cannot directly access hypervisor memory in protected
235 * kvm_nvhe_dump_backtrace - Dump KVM nVHE hypervisor backtrace.
[all …]
|
| /Linux-v6.1/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
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 …]
|
| 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 …]
|
| D | amd-memory-encryption.rst | 13 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-v6.1/arch/powerpc/platforms/pseries/ |
| D | vas.c | 25 /* The hypervisor allows one credit per window right now */
116 * The hypervisor ignores it if 0 is passed. in h_modify_vas_window()
135 * This hcall is used to determine the capabilities from the hypervisor.
137 * @query_type: If 0 is passed, the hypervisor returns the overall
139 * available. Then query the hypervisor to get the
170 * hcall to get fault CRB from the hypervisor.
190 * hypervisor to get the fault CRB on the specific fault. Then
193 * Note: The hypervisor forwards an interrupt for each fault request.
220 * state in the hypervisor. If the NX generates fault interrupt
221 * during this window, the hypervisor will not deliver this
[all …]
|
| /Linux-v6.1/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
|
| /Linux-v6.1/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 …]
|
| /Linux-v6.1/arch/arm/boot/dts/ |
| D | xenvm-4.2.dts | 20 /* 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-v6.1/tools/perf/pmu-events/arch/arm64/arm/cortex-a75/ |
| D | exception.json | 12 …hypervisor. This event counts the number of exception traps taken to EL2, excluding HVC instructio…
15 …hypervisor. This event counts the number of exception traps taken to EL2, excluding HVC instructio…
|
| /Linux-v6.1/include/xen/interface/ |
| D | xenpmu.h | 49 * everyone: itself, the hypervisor and the guests.
63 * Shared PMU data between hypervisor and PV(H) domains.
65 * The hypervisor fills out this structure during PMU interrupt and sends an
67 * Architecture-independent fields of xen_pmu_data are WO for the hypervisor
69 * by both the hypervisor and the guest (see arch-$arch/pmu.h).
|
| D | callback.h | 28 /* x86/64 hypervisor: Syscall by 64-bit guest app ('64-on-64-on-64'). */
32 * x86/32 hypervisor: Only available on x86/32 when supervisor_mode_kernel
42 * - 32-bit hypervisor: with the supervisor_mode_kernel feature enabled
43 * - 64-bit hypervisor: 32-bit guest applications on Intel CPUs
51 * x86/64 hypervisor: Syscall by 32-bit guest app on AMD CPUs
|
| /Linux-v6.1/drivers/virt/ |
| D | Kconfig | 21 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-v6.1/arch/arm64/kernel/ |
| D | hyp-stub.S | 3 * Hypervisor stub
255 * __hyp_set_vectors: Call this after boot to set the initial hypervisor
256 * vectors as part of hypervisor installation. On an SMP system, this should
262 * Before calling this, you must check that the stub hypervisor is installed
266 * If not, there is a pre-existing hypervisor, some CPUs failed to boot, or
268 * hypervisor is unlikely to work as desired.
270 * When you call into your shiny new hypervisor, sp_el2 will contain junk,
271 * so you will need to set that to something sensible at the new hypervisor's
|
12345678910>>...31
