On Wed, Dec 06, 2017 at 03:50:14PM +0800, Chao Gao wrote: > Signed-off-by: Chao Gao <[email protected]> > --- > xen/include/public/hvm/hvm_info_table.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/xen/include/public/hvm/hvm_info_table.h > b/xen/include/public/hvm/hvm_info_table.h > index 08c252e..6833a4c 100644 > --- a/xen/include/public/hvm/hvm_info_table.h > +++ b/xen/include/public/hvm/hvm_info_table.h > @@ -32,7 +32,7 @@ > #define HVM_INFO_PADDR ((HVM_INFO_PFN << 12) + HVM_INFO_OFFSET) > > /* Maximum we can support with current vLAPIC ID mapping. */ > -#define HVM_MAX_VCPUS 128 > +#define HVM_MAX_VCPUS 512
I checked a few places where this is used, bumping the number doesn't seem to be harmful on the surface. Of course there is the question how many CPUs can upstream support, I think it is still under argument at the moment. Wei. _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
