KVM: x86: bump MAX_VCPUS to 288
288 is in high demand because of Knights Landing CPU. We cannot set the limit to 640k, because that would be wasting space. Reviewed-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Radim Krčmář <rkrcmar@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
This commit is contained in:
Родитель
c519265f2a
Коммит
682f732ecf
|
@ -34,7 +34,7 @@
|
||||||
#include <asm/asm.h>
|
#include <asm/asm.h>
|
||||||
#include <asm/kvm_page_track.h>
|
#include <asm/kvm_page_track.h>
|
||||||
|
|
||||||
#define KVM_MAX_VCPUS 255
|
#define KVM_MAX_VCPUS 288
|
||||||
#define KVM_SOFT_MAX_VCPUS 240
|
#define KVM_SOFT_MAX_VCPUS 240
|
||||||
#define KVM_USER_MEM_SLOTS 509
|
#define KVM_USER_MEM_SLOTS 509
|
||||||
/* memory slots that are not exposed to userspace */
|
/* memory slots that are not exposed to userspace */
|
||||||
|
|
Загрузка…
Ссылка в новой задаче