aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing/selftests/kvm/dirty_log_perf_test.c
diff options
context:
space:
mode:
authorJuergen Gross <jgross@suse.com>2021-07-01 17:41:00 +0200
committerPaolo Bonzini <pbonzini@redhat.com>2021-07-27 16:58:59 -0400
commit76b4f357d0e7d8f6f0013c733e6cba1773c266d3 (patch)
treecd74eea0d03255b4dfe5d3a253b327be8a63d28b /tools/testing/selftests/kvm/dirty_log_perf_test.c
parentKVM: x86: Check the right feature bit for MSR_KVM_ASYNC_PF_ACK access (diff)
downloadlinux-dev-76b4f357d0e7d8f6f0013c733e6cba1773c266d3.tar.xz
linux-dev-76b4f357d0e7d8f6f0013c733e6cba1773c266d3.zip
x86/kvm: fix vcpu-id indexed array sizes
KVM_MAX_VCPU_ID is the maximum vcpu-id of a guest, and not the number of vcpu-ids. Fix array indexed by vcpu-id to have KVM_MAX_VCPU_ID+1 elements. Note that this is currently no real problem, as KVM_MAX_VCPU_ID is an odd number, resulting in always enough padding being available at the end of those arrays. Nevertheless this should be fixed in order to avoid rare problems in case someone is using an even number for KVM_MAX_VCPU_ID. Signed-off-by: Juergen Gross <jgross@suse.com> Message-Id: <20210701154105.23215-2-jgross@suse.com> Cc: stable@vger.kernel.org Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/testing/selftests/kvm/dirty_log_perf_test.c')
0 files changed, 0 insertions, 0 deletions