c9d2fb7d40
Xen-related Kconfig options were highly dependand on BOARD/SOC xenvm. It is not correct because Xen support may be used on any board and SoC. So, Kconfig structure was refactored, now CONFIG_XEN is located in arch/ directory (same as in Linux kernel) and can be selected for any Cortex-A arm64 setup (no other platforms are currently supported). Also remove confusion in Domain 0 naming: Domain-0, initial domain, Dom0, privileged domain etc. Now all options related to Xen Domain 0 will be controlled by CONFIG_XEN_DOM0. Signed-off-by: Dmytro Firsov <dmytro_firsov@epam.com>
26 lines
592 B
Plaintext
26 lines
592 B
Plaintext
# SPDX-License-Identifier: Apache-2.0
|
|
# Copyright (c) 2022-2023 EPAM Systems
|
|
|
|
if XEN
|
|
|
|
menu "Xen drivers"
|
|
|
|
config XEN_GRANT_TABLE
|
|
bool "Xen grant table driver"
|
|
depends on HEAP_MEM_POOL_SIZE > 0
|
|
default y
|
|
help
|
|
Xen grant table driver. Please note that driver uses dynamic memory
|
|
allocation with k_malloc(), so CONFIG_HEAP_MEM_POOL_SIZE should be
|
|
>= number of pages, that you want to alloc and grant or foreign frames
|
|
that you want to map.
|
|
|
|
config XEN_GRANT_TABLE_INIT_PRIORITY
|
|
int "Grant table driver init priority"
|
|
depends on XEN_GRANT_TABLE
|
|
default 50
|
|
|
|
endmenu
|
|
|
|
endif # XEN
|