Searched refs:hypervisor (Results 1 – 25 of 245) sorted by relevance
12345678910
1 What: /sys/hypervisor/compilation/compile_date6 Contains the build time stamp of the Xen hypervisor8 in the hypervisor.10 What: /sys/hypervisor/compilation/compiled_by15 Contains information who built the Xen hypervisor17 in the hypervisor.19 What: /sys/hypervisor/compilation/compiler24 Compiler which was used to build the Xen hypervisor26 in the hypervisor.28 What: /sys/hypervisor/properties/capabilities[all …]
1 What: /sys/hypervisor/guest_type12 What: /sys/hypervisor/pmu/pmu_mode24 privileged (e.g. dom0), the hypervisor25 "all" The guest can profile itself, the hypervisor30 What: /sys/hypervisor/pmu/pmu_features39 What: /sys/hypervisor/properties/buildid44 Build id of the hypervisor, needed for hypervisor live patching.46 in the hypervisor.
8 hypervisor layer when running Linux as a hypervisor (for example10 hypervisor when running as a guest (under Xen, KVM or any other11 hypervisor), or any hypervisor-specific interaction when the kernel is16 booted at HYP. It can also be used by a hypervisor other than KVM19 On arm and arm64 (without VHE), the kernel doesn't run in hypervisor21 hypervisor to be either installed or torn down.28 Unless specified otherwise, any built-in hypervisor must implement36 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,
12 some hypervisor service calls to support a paravirtualized guest obtaining a32 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
24 interface between the hypervisor and a management partition. This interface47 application using a combination of HMC to hypervisor interfaces and50 The set of HMC to hypervisor messages supported by the management51 application component are passed to the hypervisor over a VMC interface,68 for communicating between the management application and the hypervisor. It75 defined that must take place to establish that both the hypervisor and80 when the hypervisor detects one of the peer partitions has abnormally86 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 …]
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 */
14 normal functionality of a hypervisor must be moved into the guest. This is17 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. Guests68 can make a hypercall to the hypervisor to handle the #VE.80 hypervisor. For such cases, the Intel TDX module architecture defines two83 - Bit fields for which the hypervisor controls the value seen by the guest86 - Bit fields for which the hypervisor configures the value such that the88 fields, the hypervisor can mask off the native values, but it can not92 not know how to handle. The guest kernel may ask the hypervisor for the[all …]
6 The ACRN Hypervisor is a Type 1 hypervisor, running directly on bare-metal13 hypervisor services to the ACRN userspace.38 ioctls to communicate with the HSM. HSM implements hypervisor services by42 The ACRN hypervisor is open for contribution from anyone. The source repo is43 available at https://github.com/projectacrn/acrn-hypervisor.
6 An I/O request of a User VM, which is constructed by the hypervisor, is15 communication between the hypervisor and Service VM. An I/O request is a17 an I/O handler of the hypervisor when a trapped I/O access happens in a User19 the GPA (Guest Physical Address) of the buffer to the hypervisor. The buffer is81 An I/O request in COMPLETE or FREE state is owned by the hypervisor. HSM and87 a. The I/O handler of the hypervisor will fill an I/O request with PENDING89 b. The hypervisor makes an upcall, which is a notification interrupt, to96 f. The HSM updates I/O requests states to COMPLETE and notifies the hypervisor
12 operating system and how it should interact with the hypervisor for15 - **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 called24 issue hypercalls to the hypervisor whenever it needs to perform an action25 that is hypervisor privileged [3]_ or for other services managed by the26 hypervisor.29 asking hypervisor to perform a privileged operation on behalf of the guest. The30 guest issues a with necessary input operands. The hypervisor after performing36 The ABI specification for a hcall between a pseries guest and PAPR hypervisor43 Once control returns back to the guest after hypervisor has serviced the[all …]
51 ${resp}= Redfish.Patch /redfish/v1/Systems/hypervisor/EthernetInterfaces/${interface}94 ... /redfish/v1/Systems/hypervisor/EthernetInterfaces/${interface}117 ... /redfish/v1/Systems/hypervisor/EthernetInterfaces/${interface}123 ... /redfish/v1/Systems/hypervisor/EthernetInterfaces/${interface}138 ... /redfish/v1/Systems/hypervisor/EthernetInterfaces/${interface}171 ${resp}= Redfish.Get /redfish/v1/Systems/hypervisor/EthernetInterfaces193 ${resp}= Redfish.Get /redfish/v1/Systems/hypervisor/EthernetInterfaces202 ... /redfish/v1/Systems/hypervisor/EthernetInterfaces/eth${i}238 ... /redfish/v1/Systems/hypervisor/EthernetInterfaces/${interface}244 ... /redfish/v1/Systems/hypervisor/EthernetInterfaces/${interface}[all …]
9 On POWER based servers, a hypervisor firmware manages and allocates resources to10 the logical partitions running on the server. If this hypervisor encounters an19 from the hypervisor memory.41 - **Hypervisor**: A hypervisor (or virtual machine monitor, VMM) is a computer46 faults in hypervisor.51 - **Terminate Immediate (TI)**: A condition when the hypervisor encountered a81 memory preserved reboot. Once the system finished booting, the hypervisor96 - The hypervisor should send a special attention to BMC to notify about a severe99 - BMC should receive special TI attention from hypervisor110 - Once the dump is generated, the hypervisor should notify BMC.[all …]
1 * Xen hypervisor device tree bindings3 Xen ARM virtual platforms shall have a top-level "hypervisor" node with23 under /hypervisor with following parameters:45 hypervisor {60 they differ because they are provided by the Xen hypervisor, together with a set
2 sPAPR hypervisor calls6 a set of hypervisor calls (a.k.a. hcalls) defined in the Linux on Power9 which is what PowerVM, the IBM proprietary hypervisor, adheres to.13 In addition to those calls, we have added our own private hypervisor31 calls our private H_RTAS hypervisor call to pass the RTAS calls to QEMU.53 PAPR and LoPAR provides a set of hypervisor calls to perform cacheable or
21 Say Y here to use the hypervisor-provided Virtual Machine Generation ID28 tristate "Freescale hypervisor management driver"32 The Freescale hypervisor management driver provides several services33 to drivers and applications related to the Freescale hypervisor:
56 Failure reports will BUG() in the hypervisor. This is intended for57 local EL2 hypervisor development.62 bool "Protected KVM hypervisor stacktraces"66 Say Y here to enable pKVM hypervisor stacktraces on hyp_panic()
1 PACKAGECONFIG:append:p10bmc = " ibm-hypervisor-cert"2 PACKAGECONFIG:append:witherspoon-tacoma = " ibm-hypervisor-cert"
8 can be KVM-based or a different hypervisor). The straightforward34 hypervisor", as it itself is capable of running KVM.43 hypervisor running on bare metal, adding another layer and45 metal, running the LPAR hypervisor), L1 (host hypervisor), L246 (guest hypervisor), L3 (nested guest).62 hypervisor" (level-1 guest). This in turn allows you to create158 then the guest hypervisor will subsequently be capable of running a165 1. On the host hypervisor (L0), enable the ``nested`` parameter on175 2. The guest hypervisor (L1) must be provided with the ``sie`` CPU179 3. Now the KVM module can be loaded in the L1 (guest hypervisor)::[all …]
34 whose data will be filled in by the hypervisor. The hypervisor is only78 whose data will be filled in by the hypervisor periodically. Only one81 The hypervisor may update this structure at any time it sees fit until127 coordinated between the guest and the hypervisor. Availability224 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 content277 whose data will be filled in by the hypervisor periodically. Only one280 The hypervisor may update this structure at any time it sees fit until305 the hypervisor doesn't support this field.318 written to by the hypervisor, typically at the time of interrupt[all …]
13 virtual machines (VMs) under the control of a hypervisor. When enabled,17 The hypervisor can determine the SEV support through the CPUID54 key management interface to perform common hypervisor activities such as87 The KVM_SEV_INIT command is used by the hypervisor to initialize the SEV platform216 The KVM_SEV_DEBUG_DECRYPT command can be used by the hypervisor to request the236 The KVM_SEV_DEBUG_ENCRYPT command can be used by the hypervisor to request the256 The KVM_SEV_LAUNCH_SECRET command can be used by the hypervisor to inject secret272 __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 attestation303 The KVM_SEV_SEND_START command can be used by the hypervisor to create an[all …]
37 This property may be used in virtualized environments where the hypervisor81 The Freescale hypervisor and msi-address-6487 In a virtualized environment, the hypervisor may need to create an IOMMU88 mapping for MSIIR. The Freescale ePAPR hypervisor has this requirement90 (PAMU), which is currently the only IOMMU that the hypervisor supports.106 Therefore, the hypervisor has to create a subwindow inside the same110 address of MSIIR. The hypervisor configures the PAMU to map that address to
3 Before=mapper-wait@-xyz-openbmc_project-state-hypervisor.service6 ExecStart=/usr/bin/phosphor-hypervisor-state-manager
26 hypervisor = 'H', enumerator32 hypervisor = 0x82, enumerator
104 only possible, when the hypervisor does not sanitize the content of the174 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 amount353 managed and sanitized by the hypervisor. Though disabling EPT has a357 EPT can be disabled in the hypervisor via the 'kvm-intel.ept' parameter.385 flush Leaves SMT enabled and enables the default hypervisor394 flush,nosmt Disables SMT and enables the default hypervisor mitigation,406 off Disables hypervisor mitigations and doesn't emit any409 on both hypervisor and bare metal.[all …]
129 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()