diff options
author | Vitaly Kuznetsov <vkuznets@redhat.com> | 2020-10-01 15:05:41 +0200 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2020-10-21 17:36:33 -0400 |
commit | 3f4e3eb417b10ef45caddc4e1d3a18a34b539440 (patch) | |
tree | 659a7bd039fefee8bea2d3f94d829948f19f9b7e /arch/x86/kvm/mmu/mmu.c | |
parent | 255cbecfe0c9466ade041fe381dde18a61cca549 (diff) | |
download | lwn-3f4e3eb417b10ef45caddc4e1d3a18a34b539440.tar.gz lwn-3f4e3eb417b10ef45caddc4e1d3a18a34b539440.zip |
KVM: x86: bump KVM_MAX_CPUID_ENTRIES
As vcpu->arch.cpuid_entries is now allocated dynamically, the only
remaining use for KVM_MAX_CPUID_ENTRIES is to check KVM_SET_CPUID/
KVM_SET_CPUID2 input for sanity. Since it was reported that the
current limit (80) is insufficient for some CPUs, bump
KVM_MAX_CPUID_ENTRIES and use an arbitrary value '256' as the new
limit.
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Message-Id: <20201001130541.1398392-4-vkuznets@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'arch/x86/kvm/mmu/mmu.c')
0 files changed, 0 insertions, 0 deletions