github/acrn-hypervisor
1
0
Fork 0
mirror of https://github.com/projectacrn/acrn-hypervisor.git synced 2025-09-21 08:50:27 +00:00
Code Issues Projects Releases Wiki Activity

Kconfig: change scenario variable type to string

Browse Source 
Basicly ACRN scenario is a configuration name for specific usage. By giving
scenario name ACRN will load corresponding VM configurations to build the
hypervisor. But customer might have their own scenario name, change the
scenario type from choice to string is friendly to them since Kconfig source
file change will not be needed.

With this change, CONFIG_$(SCENARIO) will not exist in kconfig file and will
be instead of CONFIG_SCENARIO, so the Makefile need to be changed accordingly;

Tracked-On: #4616

Signed-off-by: Victor Sun <victor.sun@intel.com>
This commit is contained in:
Victor Sun
2020-04-13 09:47:26 +08:00
committed by wenlingz
parent 7282b933fb
commit dba0591f72
4 changed files with 34 additions and 88 deletions
Download Patch File Download Diff File Expand all files Collapse all files

51
hypervisor/arch/x86/Kconfig
View File

@@ -1,41 +1,18 @@
choice
prompt "ACRN Scenario"
default SDC
config SCENARIO
string "ACRN scenario"
default "sdc"
help
Select the scenario name to load corresponding VM configuration.
config SDC
bool "Software Defined Cockpit"
help
SDC (Software Defined Cockpit) is a typical scenario that ACRN supported.
SDC will have one pre-launched SOS VM and one post-launched VM.
config SDC2
bool "Software Defined Cockpit 2"
help
SDC2 (Software Defined Cockpit 2) is an extended scenario for automotive SDC system.
SDC2 will have one pre-launched SOS VM and up to three post-launched VM.
config LOGICAL_PARTITION
bool "Logical Partition VMs"
help
This scenario will run two pre-launched VMs.
config INDUSTRY
bool "Industry VMs"
help
This scenario is a typical scenario for industry usage with 4 VMs:
one pre-launched SOS VM, one post-launched Standard VM for HMI, one or two
post-launched RT VM for real-time control.
config HYBRID
bool "Hybrid VMs"
help
This scenario is a typical scenario for hybrid usage with 3 VMs:
one pre-launched VM, one pre-launched SOS VM and one post-launched Standard
VM.
endchoice
By specifying SCENARIO name, ACRN will load corresponding VM configurations
to build the hypervisor. Currently ACRN provides below reference scenarios:
sdc: Typical scenario for automotive Software Defined Cockpit system.
sdc will have one pre-launched SOS VM and one post-launched VM;
sdc2: Extended scenario for automotive Software Defined Cockpit system.
sdc2 will have one pre-launched SOS VM and up to three post-launched VMs;
industry: Typical scenario for industry usage with 3 VMs: one pre-launched SOS VM,
one post-launched Standard VM for HMI, one post-launched RT VM for real-time control.
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;
config MULTIBOOT2
bool "Multiboot2 support"