From: Andrew Jones <drjones@redhat.com>
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com, rkrcmar@redhat.com, thuth@redhat.com,
peterx@redhat.com
Subject: [PATCH v2 0/4] kvm: selftests: aarch64: use struct kvm_vcpu_init
Date: Mon, 27 May 2019 16:31:37 +0200 [thread overview]
Message-ID: <20190527143141.13883-1-drjones@redhat.com> (raw)
aarch64 vcpu setup requires a vcpu init step that takes a kvm_vcpu_init
struct. So far we've just hard coded that to be one that requests no
features and always uses KVM_ARM_TARGET_GENERIC_V8 for the target. We
should have used the preferred target from the beginning, so we do that
now, and we also provide an API to unit tests to select a target of their
choosing and/or cpu features.
Switching to the preferred target fixes running on platforms that don't
like KVM_ARM_TARGET_GENERIC_V8. The new API will be made use of with
some coming unit tests.
v2:
- rename vm_vcpu_add_memslots to vm_vcpu_add_with_memslots
Andrew Jones (4):
kvm: selftests: rename vm_vcpu_add to vm_vcpu_add_with_memslots
kvm: selftests: introduce vm_vcpu_add
kvm: selftests: introduce aarch64_vcpu_setup
kvm: selftests: introduce aarch64_vcpu_add_default
.../selftests/kvm/include/aarch64/processor.h | 4 +++
.../testing/selftests/kvm/include/kvm_util.h | 5 +--
.../selftests/kvm/lib/aarch64/processor.c | 33 +++++++++++++++----
tools/testing/selftests/kvm/lib/kvm_util.c | 29 +++++++++++++---
.../selftests/kvm/lib/x86_64/processor.c | 2 +-
.../testing/selftests/kvm/x86_64/evmcs_test.c | 2 +-
.../kvm/x86_64/kvm_create_max_vcpus.c | 2 +-
tools/testing/selftests/kvm/x86_64/smm_test.c | 2 +-
.../testing/selftests/kvm/x86_64/state_test.c | 2 +-
9 files changed, 63 insertions(+), 18 deletions(-)
--
2.20.1
next reply other threads:[~2019-05-27 14:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 14:31 Andrew Jones [this message]
2019-05-27 14:31 ` [PATCH v2 1/4] kvm: selftests: rename vm_vcpu_add to vm_vcpu_add_with_memslots Andrew Jones
2019-05-28 2:14 ` Peter Xu
2019-05-27 14:31 ` [PATCH v2 2/4] kvm: selftests: introduce vm_vcpu_add Andrew Jones
2019-05-28 2:14 ` Peter Xu
2019-05-27 14:31 ` [PATCH v2 3/4] kvm: selftests: introduce aarch64_vcpu_setup Andrew Jones
2019-05-27 14:31 ` [PATCH v2 4/4] kvm: selftests: introduce aarch64_vcpu_add_default Andrew Jones
2019-06-04 17:16 ` [PATCH v2 0/4] kvm: selftests: aarch64: use struct kvm_vcpu_init Paolo Bonzini
2019-06-05 7:26 ` Peter Xu
2019-06-05 12:15 ` Paolo Bonzini
2019-06-04 17:17 ` Paolo Bonzini
2019-06-27 12:36 ` Andrew Jones
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=20190527143141.13883-1-drjones@redhat.com \
--to=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=thuth@redhat.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