From: Wei Wang <wei.w.wang@intel.com>
To: seanjc@google.com, pbonzini@redhat.com
Cc: dmatlack@google.com, vipinsh@google.com, ajones@ventanamicro.com,
eric.auger@redhat.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, Wei Wang <wei.w.wang@intel.com>
Subject: [PATCH v1 00/18] KVM selftests code consolidation and cleanup
Date: Mon, 24 Oct 2022 19:34:27 +0800 [thread overview]
Message-ID: <20221024113445.1022147-1-wei.w.wang@intel.com> (raw)
This patch series intends to improve kvm selftests with better code
consolidation using the helper functions to perform vcpu and thread
related operations.
In general, several aspects are improved:
1) The current users allocate an array of vcpu pointers to the vcpus that
are added to a vm, and an array of vcpu threads. This isn't necessary
as kvm_vm already maintains a list of added vcpus. This series changes
the list of vcpus in the kvm_vm struct to a vcpu array for users to
work with and removes each user's own allocation of such vcpu arrays.
Aslo add the vcpu thread to the kvm_vcpu struct, so that users don't
need to explicitly allocate a thread array to manage vcpu threads on
their own.
2) Change the users to use the helper functions provided by this series
with the following enhancements:
- Many users working with pthread_create/join forgot to check if
error on returning. The helper functions have handled thoses inside,
so users don't need to handle them by themselves;
- The vcpu threads created via the helper functions are named in
"vcpu-##id" format. Naming the threads facilitates debugging,
performance tuning, runtime pining etc;
- helper functions named with "vm_vcpu_threads_" iterates over all the
vcpus that have been added to the vm. Users don't need a explicit
loop to go through the added cpus by themselves.
3) kvm_vcpu is used as the interface parameter to the vcpu thread's
start routine, and the user specific data is made to be the private
data in kvm_vcpu. This can simplify the user specific data structures,
as kvm_vcpu has already included the required info for the thread, for
example, in patch 13, the cpu_idx field from "struct vcpu_thread"
is a duplicate of vcpu->id.
The changes have been tested on an SPR server. Patch 15 and 16 haven't
been tested due to the lack of an ARM environment currently.
Wei Wang (18):
KVM: selftests/kvm_util: use array of pointers to maintain vcpus in
kvm_vm
KVM: selftests/kvm_util: use vm->vcpus[] when create vm with vcpus
KVM: selftests/kvm_util: helper functions for vcpus and threads
KVM: selftests/kvm_page_table_test: vcpu related code consolidation
KVM: selftests/hardware_disable_test: code consolidation and cleanup
KVM: selftests/dirty_log_test: vcpu related code consolidation
KVM: selftests/max_guest_memory_test: vcpu related code consolidation
KVM: selftests/set_memory_region_test: vcpu related code consolidation
KVM: selftests/steal_time: vcpu related code consolidation and cleanup
KVM: selftests/tsc_scaling_sync: vcpu related code consolidation
KVM: selftest/xapic_ipi_test: vcpu related code consolidation
KVM: selftests/rseq_test: name the migration thread and some cleanup
KVM: selftests/perf_test_util: vcpu related code consolidation
KVM: selftest/memslot_perf_test: vcpu related code consolidation
KVM: selftests/vgic_init: vcpu related code consolidation
KVM: selftest/arch_timer: vcpu related code consolidation
KVM: selftests: remove the *vcpu[] input from __vm_create_with_vcpus
KVM: selftests/kvm_create_max_vcpus: check KVM_MAX_VCPUS
.../selftests/kvm/aarch64/arch_timer.c | 42 ++--
.../testing/selftests/kvm/aarch64/vgic_init.c | 35 ++-
.../selftests/kvm/access_tracking_perf_test.c | 18 +-
.../selftests/kvm/demand_paging_test.c | 9 +-
.../selftests/kvm/dirty_log_perf_test.c | 11 +-
tools/testing/selftests/kvm/dirty_log_test.c | 16 +-
.../selftests/kvm/hardware_disable_test.c | 56 ++---
.../testing/selftests/kvm/include/kvm_util.h | 24 ++
.../selftests/kvm/include/kvm_util_base.h | 12 +-
.../selftests/kvm/include/perf_test_util.h | 9 +-
.../selftests/kvm/kvm_create_max_vcpus.c | 7 +
.../selftests/kvm/kvm_page_table_test.c | 16 +-
tools/testing/selftests/kvm/lib/kvm_util.c | 217 +++++++++++++++---
.../selftests/kvm/lib/perf_test_util.c | 68 ++----
.../selftests/kvm/lib/x86_64/perf_test_util.c | 11 +-
tools/testing/selftests/kvm/lib/x86_64/vmx.c | 2 +-
.../selftests/kvm/max_guest_memory_test.c | 53 ++---
.../kvm/memslot_modification_stress_test.c | 9 +-
.../testing/selftests/kvm/memslot_perf_test.c | 137 +++++------
tools/testing/selftests/kvm/rseq_test.c | 10 +-
.../selftests/kvm/set_memory_region_test.c | 16 +-
tools/testing/selftests/kvm/steal_time.c | 15 +-
.../selftests/kvm/x86_64/tsc_scaling_sync.c | 25 +-
.../selftests/kvm/x86_64/xapic_ipi_test.c | 54 ++---
24 files changed, 476 insertions(+), 396 deletions(-)
--
2.27.0
next reply other threads:[~2022-10-24 11:37 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 11:34 Wei Wang [this message]
2022-10-24 11:34 ` [PATCH v1 01/18] KVM: selftests/kvm_util: use array of pointers to maintain vcpus in kvm_vm Wei Wang
2022-10-26 23:47 ` Sean Christopherson
2022-10-27 12:28 ` Wang, Wei W
2022-10-27 15:27 ` Sean Christopherson
2022-10-28 2:13 ` Wang, Wei W
2022-10-24 11:34 ` [PATCH v1 02/18] KVM: selftests/kvm_util: use vm->vcpus[] when create vm with vcpus Wei Wang
2022-10-24 11:34 ` [PATCH v1 03/18] KVM: selftests/kvm_util: helper functions for vcpus and threads Wei Wang
2022-10-27 0:09 ` Sean Christopherson
2022-10-27 14:02 ` Wang, Wei W
2022-10-27 14:54 ` Sean Christopherson
2022-10-24 11:34 ` [PATCH v1 04/18] KVM: selftests/kvm_page_table_test: vcpu related code consolidation Wei Wang
2022-10-24 11:34 ` [PATCH v1 05/18] KVM: selftests/hardware_disable_test: code consolidation and cleanup Wei Wang
2022-10-27 0:16 ` Sean Christopherson
2022-10-27 14:14 ` Wang, Wei W
2022-10-27 18:03 ` Sean Christopherson
2022-10-28 2:16 ` Wang, Wei W
2022-10-24 11:34 ` [PATCH v1 06/18] KVM: selftests/dirty_log_test: vcpu related code consolidation Wei Wang
2022-10-24 11:34 ` [PATCH v1 07/18] KVM: selftests/max_guest_memory_test: " Wei Wang
2022-10-24 11:34 ` [PATCH v1 08/18] KVM: selftests/set_memory_region_test: " Wei Wang
2022-10-24 11:34 ` [PATCH v1 09/18] KVM: selftests/steal_time: vcpu related code consolidation and cleanup Wei Wang
2022-10-27 0:17 ` Sean Christopherson
2022-10-24 11:34 ` [PATCH v1 10/18] KVM: selftests/tsc_scaling_sync: vcpu related code consolidation Wei Wang
2022-10-24 11:34 ` [PATCH v1 11/18] KVM: selftest/xapic_ipi_test: " Wei Wang
2022-10-24 11:34 ` [PATCH v1 12/18] KVM: selftests/rseq_test: name the migration thread and some cleanup Wei Wang
2022-10-27 0:18 ` Sean Christopherson
2022-10-24 11:34 ` [PATCH v1 13/18] KVM: selftests/perf_test_util: vcpu related code consolidation Wei Wang
2022-10-24 11:34 ` [PATCH v1 14/18] KVM: selftest/memslot_perf_test: " Wei Wang
2022-10-24 11:34 ` [PATCH v1 15/18] KVM: selftests/vgic_init: " Wei Wang
2022-10-24 11:34 ` [PATCH v1 16/18] KVM: selftest/arch_timer: " Wei Wang
2022-10-24 11:34 ` [PATCH v1 17/18] KVM: selftests: remove the *vcpu[] input from __vm_create_with_vcpus Wei Wang
2022-10-24 11:34 ` [PATCH v1 18/18] KVM: selftests/kvm_create_max_vcpus: check KVM_MAX_VCPUS Wei Wang
2022-10-27 0:22 ` Sean Christopherson
2022-10-26 21:22 ` [PATCH v1 00/18] KVM selftests code consolidation and cleanup David Matlack
2022-10-27 12:18 ` Wang, Wei W
2022-10-27 15:44 ` Sean Christopherson
2022-10-27 16:24 ` David Matlack
2022-10-27 18:27 ` Sean Christopherson
2022-10-28 12:41 ` Andrew Jones
2022-10-28 15:49 ` Sean Christopherson
2022-11-07 18:11 ` David Matlack
2022-11-07 18:19 ` Sean Christopherson
2022-11-09 19:05 ` David Matlack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221024113445.1022147-1-wei.w.wang@intel.com \
--to=wei.w.wang@intel.com \
--cc=ajones@ventanamicro.com \
--cc=dmatlack@google.com \
--cc=eric.auger@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=vipinsh@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox