| /openbmc/linux/Documentation/ABI/stable/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/powerpc/ |
| H A 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 …]
|
| /openbmc/phosphor-state-manager/ |
| H A D | hypervisor_state_manager.hpp | 31 class Hypervisor : public HypervisorInherit class
34 Hypervisor() = delete;
35 Hypervisor(const Hypervisor&) = delete;
36 Hypervisor& operator=(const Hypervisor&) = delete;
37 Hypervisor(Hypervisor&&) = delete;
38 Hypervisor& operator=(Hypervisor&&) = delete;
39 ~Hypervisor() override = default;
41 /** @brief Constructs Hypervisor State Manager
46 Hypervisor(sdbusplus::bus_t& bus, const char* objPath) : in Hypervisor() function in phosphor::state::manager::Hypervisor
68 /** @brief Check if BootProgress change affects hypervisor state
[all …]
|
| H A D | hypervisor_state_manager.cpp | 28 server::Host::Transition Hypervisor::requestedHostTransition(Transition value) in requestedHostTransition()
30 info("Hypervisor state transition request of {TRAN_REQUEST}", in requestedHostTransition()
36 error("Hypervisor state only supports a transition to On"); in requestedHostTransition()
42 // which is responsible for propagating the On request to the hypervisor in requestedHostTransition()
47 server::Host::HostState Hypervisor::currentHostState(HostState value) in currentHostState()
52 info("Change to Hypervisor State: {HYP_STATE}", "HYP_STATE", value); in currentHostState()
57 server::Host::HostState Hypervisor::currentHostState() const in currentHostState()
62 void Hypervisor::updateCurrentHostState(std::string& bootProgress) in updateCurrentHostState()
88 // set hypervisor state to off in updateCurrentHostState()
93 void Hypervisor::bootProgressChangeEvent(sdbusplus::message_t& msg) in bootProgressChangeEvent()
|
| /openbmc/bmcweb/redfish-core/lib/ |
| H A D | hypervisor_system.hpp | 30 * @brief Retrieves hypervisor state properties over dbus
32 * The hypervisor state object is optional so this function will only set the
42 BMCWEB_LOG_DEBUG("Get hypervisor state information."); in getHypervisorState()
44 "xyz.openbmc_project.State.Hypervisor", in getHypervisorState()
57 BMCWEB_LOG_DEBUG("Hypervisor state: {}", hostState); in getHypervisorState()
115 * @brief Populate Actions if any are valid for hypervisor object
117 * The hypervisor state object is optional so this function will only set the
127 BMCWEB_LOG_DEBUG("Get hypervisor actions."); in getHypervisorActions()
153 // More then one hypervisor object is not supported and is an in getHypervisorActions()
163 "/redfish/v1/Systems/hypervisor/Actions/ComputerSystem.Reset"; in getHypervisorActions()
[all …]
|
| /openbmc/docs/designs/ |
| H A D | power-systems-memory-preserving-reboot.md | 9 On POWER based servers, a hypervisor firmware manages and allocates resources to
10 the logical partitions running on the server. If this hypervisor encounters an
19 from the hypervisor memory.
41 - **Hypervisor**: A hypervisor (or virtual machine monitor, VMM) is a computer
43 [read more](https://en.wikipedia.org/wiki/Hypervisor)
46 faults in hypervisor.
51 - **Terminate Immediate (TI)**: A condition when the hypervisor encountered a
81 memory preserved reboot. Once the system finished booting, the hypervisor
96 - The hypervisor should send a special attention to BMC to notify about a severe
99 - BMC should receive special TI attention from hypervisor
[all …]
|
| /openbmc/linux/Documentation/virt/kvm/arm/ |
| H A 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,
|
| /openbmc/linux/Documentation/misc-devices/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A 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.
|
| /openbmc/linux/Documentation/virt/acrn/ |
| H A 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.
|
| H A 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
|
| /openbmc/linux/drivers/tty/hvc/ |
| H A 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"
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | acrn.h | 3 * Userspace interface for /dev/acrn_hsm - ACRN Hypervisor Service Module
89 * @completion_polling: Polling flag. Hypervisor will poll completion of the
105 * An I/O request in COMPLETE or FREE state is owned by the hypervisor. HSM and
115 * | hypervisor:
131 * | notifies the hypervisor
133 * | hypervisor:
136 * | hypervisor:
144 * Atomic and barriers are required when HSM and hypervisor accessing the state
184 * @vmid: User VM ID returned from the hypervisor
186 * @vcpu_num: Number of vCPU in the VM. Return from hypervisor.
[all …]
|
| H A 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
|
| /openbmc/linux/arch/arm64/kvm/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/virt/kvm/x86/ |
| H A 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 …]
|
| H A 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 …]
|
| /openbmc/linux/arch/arm64/kernel/ |
| H A D | hyp-stub.S | 3 * Hypervisor stub
87 0: // Check whether we only want the hypervisor to run VHE, not the kernel
206 * __hyp_set_vectors: Call this after boot to set the initial hypervisor
207 * vectors as part of hypervisor installation. On an SMP system, this should
213 * Before calling this, you must check that the stub hypervisor is installed
217 * If not, there is a pre-existing hypervisor, some CPUs failed to boot, or
219 * hypervisor is unlikely to work as desired.
221 * When you call into your shiny new hypervisor, sp_el2 will contain junk,
222 * so you will need to set that to something sensible at the new hypervisor's
|
| /openbmc/phosphor-networkd/src/ibm/hypervisor-network-mgr-src/ |
| H A D | hyp_network_manager_main.cpp | 7 "/xyz/openbmc_project/network/hypervisor";
9 "xyz.openbmc_project.Network.Hypervisor";
29 // Create hypervisor network manager dbus object in main()
32 // Create the hypervisor eth interface objects in main()
35 // Create the hypervisor system config object in main()
|
| /openbmc/phosphor-state-manager/service_files/ |
| H A D | xyz.openbmc_project.State.Hypervisor.service | 2 Description=Phosphor Hypervisor State Manager
3 Before=mapper-wait@-xyz-openbmc_project-state-hypervisor.service
6 ExecStart=/usr/bin/phosphor-hypervisor-state-manager
9 BusName=xyz.openbmc_project.State.Hypervisor
|
| /openbmc/linux/arch/powerpc/platforms/pseries/ |
| H A D | vas.c | 26 /* The hypervisor allows one credit per window right now */
117 * The hypervisor ignores it if 0 is passed. in h_modify_vas_window()
136 * This hcall is used to determine the capabilities from the hypervisor.
138 * @query_type: If 0 is passed, the hypervisor returns the overall
140 * available. Then query the hypervisor to get the
171 * hcall to get fault CRB from the hypervisor.
191 * hypervisor to get the fault CRB on the specific fault. Then
194 * Note: The hypervisor forwards an interrupt for each fault request.
221 * state in the hypervisor. If the NX generates fault interrupt
222 * during this window, the hypervisor will not deliver this
[all …]
|
| /openbmc/openbmc/meta-ibm/recipes-phosphor/settings/phosphor-settings-manager/ |
| H A D | HypervisorInterface-default-p10bmc.override.yml | 1 /xyz/openbmc_project/network/hypervisor:
7 /xyz/openbmc_project/network/hypervisor/eth0:
20 /xyz/openbmc_project/network/hypervisor/eth0/ipv4/addr0:
40 /xyz/openbmc_project/network/hypervisor/eth1:
53 /xyz/openbmc_project/network/hypervisor/eth1/ipv4/addr0:
|
| /openbmc/qemu/docs/specs/ |
| H A D | ppc-spapr-hcalls.rst | 2 sPAPR hypervisor calls
6 a set of hypervisor calls (a.k.a. hcalls) defined in the Linux on Power
9 which is what PowerVM, the IBM proprietary hypervisor, adheres to.
13 In addition to those calls, we have added our own private hypervisor
31 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
|
| /openbmc/linux/tools/perf/pmu-events/arch/arm64/arm/cortex-a75/ |
| H A 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…
|