Searched full:hypervisor (Results 1 – 25 of 34) sorted by relevance
12
| /Zephyr-Core-3.5.0/drivers/serial/ |
| D | Kconfig.xen | 1 # Xen hypervisor console via UART setup
8 bool "Xen hypervisor DomU console UART driver"
15 Enable Xen ring buffer based hypervisor console driver. Used
19 bool "Xen hypervisor consoleio UART driver"
24 Enable Xen hypervisor console driver. Used for Zephyr as
31 int "Xen hypervisor console init priority"
|
| /Zephyr-Core-3.5.0/arch/arm64/core/xen/ |
| D | Kconfig | 1 # Xen hypervisor configuration options
12 Enables support of Xen hypervisor on arm64 platform. Get enabled
13 when board device tree contains "hypervisor" node with "xen,xen"
|
| D | enlighten.c | 23 * where hypervisor shared_info will be mapped. k_aligned_alloc() is not
|
| /Zephyr-Core-3.5.0/arch/arm64/core/ |
| D | smccc-call.S | 9 * Monitor Call (SMC) and Hypervisor Call (HVC).
39 * handled by a hypervisor running in EL2.
|
| D | reset.c | 151 * Enable this if/when we use the hypervisor timer. in z_arm64_el2_init()
|
| /Zephyr-Core-3.5.0/snippets/xen_dom0/boards/ |
| D | rcar_salvator_xs_m3.overlay | 19 hypervisor: hypervisor@88080000 {
|
| D | rcar_h3ulcb_ca57.overlay | 19 hypervisor: hypervisor@88080000 {
|
| D | qemu_cortex_a53.overlay | 23 hypervisor: hypervisor@40200000 {
|
| /Zephyr-Core-3.5.0/boards/x86/acrn/doc/ |
| D | index.rst | 5 hypervisor (see https://projectacrn.org/). The process for getting
8 ACRN hypervisor supports a hybrid scenario where Zephyr runs in a so-
10 hypervisor directly without involving the SOS VM. This is the most
24 and ACRN hypervisor to demonstrate that it works successfully. To learn more about
57 git clone https://github.com/projectacrn/acrn-hypervisor
59 We suggest that you use versions v2.5.1 or later of the ACRN hypervisor
152 This configures ACRN to run Zephyr on CPU0 and CPU1. The ACRN hypervisor
196 ``build/hypervisor/acrn.bin``
255 # cp $PATH_TO_ACRN/build/hypervisor/acrn.bin /mnt/acrn/efi/boot/
|
| /Zephyr-Core-3.5.0/drivers/virtualization/ |
| D | Kconfig | 20 present in ACRN hypervisor, and lets VM sharing memory with each
67 ivshmem-v2 is primarily used for IPC in the Jailhouse hypervisor.
|
| /Zephyr-Core-3.5.0/boards/arm64/xenvm/ |
| D | xenvm.dts | 70 hypervisor: hypervisor@38000000 { label
|
| /Zephyr-Core-3.5.0/dts/bindings/virtualization/ |
| D | qemu,ivshmem.yaml | 16 Primarily used for IPC in the Jailhouse hypervisor.
|
| /Zephyr-Core-3.5.0/drivers/ethernet/ |
| D | Kconfig.ivshmem | 15 Used for Ethernet communication between "cells" in the Jailhouse hypervisor.
|
| /Zephyr-Core-3.5.0/snippets/xen_dom0/ |
| D | README.rst | 16 * add correct memory and hypervisor nodes, based on regions Xen picked for Domain-0 on your setup.
49 This will start you a Xen hypervisor with your application as Xen control domain. To make it usable,
|
| /Zephyr-Core-3.5.0/include/zephyr/xen/public/ |
| D | arch-arm.h | 41 * respectively irrespective of whether the underlying hypervisor is
67 * (including the hypervisor and other guests) must reside in memory
73 * - memory shared with the hypervisor (struct shared_info, struct
151 * hypervisor node on device tree can be used as target gpfn for the
163 * interrupt specified under the Xen compatible hypervisor node on
393 * hypervisor. Guests must not rely on these hardcoded values but
|
| /Zephyr-Core-3.5.0/include/zephyr/sip_svc/ |
| D | sip_svc.h | 15 * SMC/HVC call from kernel running at EL1 to hypervisor/secure
67 * with hypervisor/secure monitor firmware running at EL2/EL3.
101 * SMC/HVC to hypervisor/secure monitor firmware running at EL2/EL3.
|
| /Zephyr-Core-3.5.0/samples/drivers/ethernet/eth_ivshmem/ |
| D | README.rst | 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
|
| /Zephyr-Core-3.5.0/doc/services/virtualization/ |
| D | ivshmem.rst | 48 This is primarily used for IPC in the Jailhouse hypervisor
|
| /Zephyr-Core-3.5.0/include/zephyr/arch/arm64/ |
| D | sys_io.h | 34 * Such instructions produce invalid syndrome in HSR register, so hypervisor
|
| /Zephyr-Core-3.5.0/boards/arm64/mimx93_evk/doc/ |
| D | index.rst | 146 Jailhouse is a light-weight hypervisor that allows the partitioning of hardware resources.
181 The hypervisor restricts inmate's/root's access to certain hardware resources using
|
| /Zephyr-Core-3.5.0/doc/connectivity/bluetooth/autopts/ |
| D | autopts-linux.rst | 51 Choose and install your hypervisor like VMWare Workstation(preferred) or
345 settings. Note that a host with 4 CPUs could be not enough with VirtualBox as hypervisor.
|
| /Zephyr-Core-3.5.0/boards/arm64/mimx8mm_evk/doc/ |
| D | index.rst | 115 Use Jailhouse hypervisor, after root cell linux is up:
|
| /Zephyr-Core-3.5.0/boards/arm64/mimx8mn_evk/doc/ |
| D | index.rst | 115 Use Jailhouse hypervisor, after root cell linux is up:
|
| /Zephyr-Core-3.5.0/boards/arm64/mimx8mp_evk/doc/ |
| D | index.rst | 114 Use Jailhouse hypervisor, after root cell linux is up:
|
| /Zephyr-Core-3.5.0/drivers/timer/ |
| D | apic_tsc.c | 129 /* But don't touch it on ACRN, where an hypervisor bug in clear_tsc_adjust()
|
12
