Searched full:hypervisor (Results 1 – 25 of 39) sorted by relevance
12
1 # Xen hypervisor console via UART setup8 bool "Xen hypervisor DomU console UART driver"15 Enable Xen ring buffer based hypervisor console driver. Used19 bool "Xen hypervisor consoleio UART driver"24 Enable Xen hypervisor console driver. Used for Zephyr as31 int "Xen hypervisor console init priority"
1 # Xen hypervisor configuration options12 Enables support of Xen hypervisor on arm64 platform. Get enabled13 when board device tree contains "hypervisor" node with "xen,xen"35 interface that Zephyr will use to communicate with the hypervisor.
23 * where hypervisor shared_info will be mapped. k_aligned_alloc() is not
4 full_name: ACRN hypervisor9 full_name: ACRN on EHL hypervisor
159 * a7 Hypervisor Client ID register168 * a7 Hypervisor Client ID register215 * a7 Hypervisor Client ID register251 * a7 Hypervisor Client ID register283 * a7 Hypervisor Client ID register336 * a7 Hypervisor Client ID register367 * a7 Hypervisor Client ID register417 * Hypervisor issues this call during virtual machine (guest) creation.424 * a1 Hypervisor Client ID of newly created virtual machine426 * a7 Hypervisor Client ID register. Must be 0, because only hypervisor[all …]
1 ACRN hypervisor5 hypervisor (see https://projectacrn.org/). The process for getting8 ACRN hypervisor supports a hybrid scenario where Zephyr runs in a so-called10 hypervisor directly without involving the SOS VM. This is the most24 and ACRN hypervisor to demonstrate that it works successfully. To learn more about57 git clone https://github.com/projectacrn/acrn-hypervisor59 We suggest that you use versions v2.5.1 or later of the ACRN hypervisor152 This configures ACRN to run Zephyr on CPU0 and CPU1. The ACRN hypervisor196 ``build/hypervisor/acrn.bin``255 # cp $PATH_TO_ACRN/build/hypervisor/acrn.bin /mnt/acrn/efi/boot/
9 * Monitor Call (SMC) and Hypervisor Call (HVC).39 * handled by a hypervisor running in EL2.
160 * Enable this if/when we use the hypervisor timer. in z_arm64_el2_init()
23 hypervisor: hypervisor@40200000 {
19 hypervisor: hypervisor@88080000 {
21 hypervisor: hypervisor@78080000 {
20 present in ACRN hypervisor, and lets VM sharing memory with each67 ivshmem-v2 is primarily used for IPC in the Jailhouse hypervisor.
3 Xen Hypervisor
16 Primarily used for IPC in the Jailhouse hypervisor.
70 hypervisor: hypervisor@38000000 { label
15 Used for Ethernet communication between "cells" in the Jailhouse hypervisor.
16 * add correct memory and hypervisor nodes, based on regions Xen picked for Domain-0 on your setup.51 This will start you a Xen hypervisor with your application as Xen control domain. To make it usable,
41 * respectively irrespective of whether the underlying hypervisor is67 * (including the hypervisor and other guests) must reside in memory73 * - memory shared with the hypervisor (struct shared_info, struct151 * hypervisor node on device tree can be used as target gpfn for the163 * interrupt specified under the Xen compatible hypervisor node on393 * hypervisor. Guests must not rely on these hardcoded values but
15 * SMC/HVC call from kernel running at EL1 to hypervisor/secure67 * with hypervisor/secure monitor firmware running at EL2/EL3.101 * SMC/HVC to hypervisor/secure monitor firmware running at EL2/EL3.
48 This is primarily used for IPC in the Jailhouse hypervisor
5 Communicate with another "cell" in the Jailhouse hypervisor using IVSHMEM Ethernet.11 another "cell" in the Jailhouse hypervisor. Currently only the qemu_cortex_a53
34 * Such instructions produce invalid syndrome in HSR register, so hypervisor
52 Choose and install your hypervisor like VMWare Workstation(preferred) or378 settings. Note that a host with 4 CPUs could be not enough with VirtualBox as hypervisor.
94 Emit console messages to a jailhouse hypervisor debug console.
