OrgACRN
/
acrn-hypervisor
mirror of https://github.com/projectacrn/acrn-hypervisor.git
1
0
Fork 0
Code Issues Releases Wiki Activity
acrn-hypervisor/hypervisor/scenarios/industry/vm_configurations.h

32 lines
886 B
C
Raw Normal View History

hv: add scenario for the industry use case This scenario is typical for industry usage with 3 VMs: 1 pre-launched SOS VM, 1 post-launched user VM for HMI and 1 post-launched RT VM for real-time control. Tracked-On: #3039 Signed-off-by: Yan, Like <like.yan@intel.com>
2019-04-26 12:06:23 +08:00
/*
* Copyright (C) 2019 Intel Corporation. All rights reserved.
*
* SPDX-License-Identifier: BSD-3-Clause
*/
#ifndef VM_CONFIGURATIONS_H
#define VM_CONFIGURATIONS_H
HV: move sos bootargs to vm configurations Previously the bootargs of SOS_VM is stored in a text file and stitched into multiboot mods[0].string whereas the bootargs of PRE_LAUNCHED_VM is stored in vm_configurations.c. Given the mods[].string will be used to store Kernel image signature under hybrid mode, move the bootargs of SOS_VM to vm configurations also to make it consistent with PRE_LAUNCHED_VM; Tracked-On: #3214 Signed-off-by: Victor Sun <victor.sun@intel.com> Reviewed-by: Jason Chen CJ <jason.cj.chen@intel.com>
2019-06-02 23:33:24 +08:00
#include <misc_cfg.h>
hv: add one more guest VM to the industry scenario This commmit added one more guest VM to the industry scenario, to be aligned with the HLD for the industry usage. With this commit, 4 VMs could be launched at maximum: 1 SOS VM and 3 post-launced VM. Tracked-On: #3039 Signed-off-by: Yan, Like <like.yan@intel.com>
2019-05-05 10:11:35 +08:00
#define CONFIG_MAX_VM_NUM 4U
hv: add scenario for the industry use case This scenario is typical for industry usage with 3 VMs: 1 pre-launched SOS VM, 1 post-launched user VM for HMI and 1 post-launched RT VM for real-time control. Tracked-On: #3039 Signed-off-by: Yan, Like <like.yan@intel.com>
2019-04-26 12:06:23 +08:00
/* Bits mask of guest flags that can be programmed by device model. Other bits are set by hypervisor only */
#define DM_OWNED_GUEST_FLAG_MASK (GUEST_FLAG_SECURE_WORLD_ENABLED | GUEST_FLAG_LAPIC_PASSTHROUGH | \
GUEST_FLAG_RT | GUEST_FLAG_IO_COMPLETION_POLLING)
HV: move sos bootargs to vm configurations Previously the bootargs of SOS_VM is stored in a text file and stitched into multiboot mods[0].string whereas the bootargs of PRE_LAUNCHED_VM is stored in vm_configurations.c. Given the mods[].string will be used to store Kernel image signature under hybrid mode, move the bootargs of SOS_VM to vm configurations also to make it consistent with PRE_LAUNCHED_VM; Tracked-On: #3214 Signed-off-by: Victor Sun <victor.sun@intel.com> Reviewed-by: Jason Chen CJ <jason.cj.chen@intel.com>
2019-06-02 23:33:24 +08:00
#define SOS_VM_BOOTARGS SOS_ROOTFS \
"rw rootwait " \
"console=tty0 " \
SOS_CONSOLE \
"consoleblank=0 " \
"no_timer_check " \
"quiet loglevel=3 " \
"i915.nuclear_pageflip=1 " \
"i915.avail_planes_per_pipe=0x01010F " \
"i915.domain_plane_owners=0x011111110000 " \
"i915.enable_gvt=1 " \
SOS_BOOTARGS_DIFF
hv: add scenario for the industry use case This scenario is typical for industry usage with 3 VMs: 1 pre-launched SOS VM, 1 post-launched user VM for HMI and 1 post-launched RT VM for real-time control. Tracked-On: #3039 Signed-off-by: Yan, Like <like.yan@intel.com>
2019-04-26 12:06:23 +08:00
#endif /* VM_CONFIGURATIONS_H */