hv: remove MAX_KATA_VM_NUM and CONFIG_KATA_VM

Since the UUID is not a *must* set parameter for the standard post-launched
VM which doesn't depend on any static VM configuration. We can remove
the KATA related code from hypervisor as it belongs to such VM type.

v2-->v3:
    separate the struce acrn_platform_info change of devicemodel

v1-->v2:
    update the subject and commit msg

Tracked-On:#6685
Signed-off-by: Chenli Wei <chenli.wei@intel.com>
Reviewed-by: Wang, Yu1 <yu1.wang@intel.com>
This commit is contained in:
Chenli Wei
2021-11-09 10:50:40 +08:00
committed by wenlingz
parent 5078abc07b
commit 97e8c9457d
3 changed files with 1 additions and 7 deletions

View File

@@ -52,9 +52,6 @@
#define CONFIG_POST_RT_VM(idx) .load_order = POST_LAUNCHED_VM, \
.severity = SEVERITY_RTVM
#define CONFIG_KATA_VM(idx) .load_order = POST_LAUNCHED_VM, \
.severity = SEVERITY_STANDARD_VM
/* ACRN guest severity */
enum acrn_vm_severity {
SEVERITY_SAFETY_VM = 0x40U,

View File

@@ -337,10 +337,8 @@ struct acrn_platform_info {
*/
uint64_t vm_configs_addr;
/** Maximum Kata container number in Service VM */
uint64_t max_kata_containers;
/** Align the size of Configuration info to 128Bytes. */
uint8_t reserved[104];
uint8_t reserved[112];
} sw;
} __aligned(8);