HV: move CONFIG_MAX_VM_NUM to vm configurations

Now the MAX supported VM number is defined explicitly for each scenario,
so move this config from Kconfig to VM configuration.

Tracked-On: #2291

Signed-off-by: Victor Sun <victor.sun@intel.com>
Acked-by: Eddie Dong <eddie.dong@intel.com>
This commit is contained in:
Victor Sun
2019-04-04 13:33:48 +08:00
committed by Eddie Dong
parent d3e4f69595
commit 16de23d0d5
6 changed files with 7 additions and 10 deletions

View File

@@ -57,15 +57,6 @@ config RELEASE
console and hypervisor shell are available only in non-release
(i.e. debug) builds. Assertions are not effective in release builds.
config MAX_VM_NUM
int "Maximum number of VM"
range 1 8
default 4
help
The maximum number of virtual machines (VMs) the hypervisor can
support. This is customizable per the use cases of the build. For
general-purpose builds the maximum of physical cores can be used.
config MAX_VCPUS_PER_VM
int "Maximum number of VCPUs per VM"
range 1 8

View File

@@ -7,6 +7,6 @@ CONFIG_HV_RAM_START=0x6e000000
CONFIG_HV_RAM_SIZE=0x07800000
CONFIG_PLATFORM_RAM_SIZE=0x200000000
CONFIG_SOS_RAM_SIZE=0x200000000
CONFIG_UOS_RAM_SIZE=0x100000000
CONFIG_UOS_RAM_SIZE=0x200000000
CONFIG_DMAR_PARSE_ENABLED=n
CONFIG_IOMMU_BUS_NUM=0x10

View File

@@ -18,6 +18,7 @@
#include <lapic.h>
#include <vtd.h>
#include <logmsg.h>
#include <vm_configurations.h>
#define DBG_IOMMU 0