From f8883f43e9d6bc82b35df2c9c81211c1ef63a29e Mon Sep 17 00:00:00 2001 From: Geoffroy Van Cutsem Date: Mon, 24 Aug 2020 13:18:37 +0200 Subject: [PATCH] hv: enhance help text for the scenario option in Kconfig Enhance the help text that accompanies the CONFIG_SCENARIO symbol in Kconfig Tracked-On: #5203 Signed-off-by: Geoffroy Van Cutsem --- hypervisor/arch/x86/Kconfig | 20 +++++++++++++------- 1 file changed, 13 insertions(+), 7 deletions(-) diff --git a/hypervisor/arch/x86/Kconfig b/hypervisor/arch/x86/Kconfig index 7b3d49a9d..497a84fea 100644 --- a/hypervisor/arch/x86/Kconfig +++ b/hypervisor/arch/x86/Kconfig @@ -3,13 +3,19 @@ config SCENARIO default "industry" help By specifying SCENARIO name, ACRN will load corresponding VM configurations - to build the hypervisor. Currently ACRN provides below reference scenarios: - industry: Typical scenario for industry usage with 8 VMs: one pre-launched SOS VM, - one post-launched KATA VM, one post-launched RT VM for real-time control, - and up to five post-launched Standard VMs; - hybrid: Typical scenario for hybrid usage with 3 VMs: one pre-launched VM, - one pre-launched SOS VM and one post-launched Standard VM; - logical_partition: Typical scenario that run two isolated pre-launched VMs; + to build the hypervisor. Currently ACRN provides four reference scenarios: + + - industry: Typical scenario for industry usage with 8 VMs: one pre-launched SOS VM, + one post-launched KATA VM, one post-launched RT VM for real-time control, + and up to five post-launched Standard VMs; + - hybrid: Typical scenario for hybrid usage with 3 VMs: one pre-launched Safety VM, + one pre-launched Service VM and one post-launched Standard VM; + - hybrid_rt: Typical scenario for hybrid real-time usage with 3 VMs: one + pre-launched RTVM, one pre-launched Service VM and one post-launched Standard VM; + - logical_partition: Typical scenario that run two isolated pre-launched VMs + + Other values are possible if a corresponding scenario has been created + under 'misc/vm_configs/scenarios/' in the source code. config MULTIBOOT2 bool "Multiboot2 support"