From: Eric Auger <eric.auger@redhat.com>
To: eric.auger.pro@gmail.com, eric.auger@redhat.com,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
pbonzini@redhat.com, vkuznets@redhat.com
Cc: thuth@redhat.com, drjones@redhat.com, wei.huang2@amd.com
Subject: [PATCH v4 0/3] selftests: KVM: AMD Nested SVM test infrastructure
Date: Thu, 6 Feb 2020 11:47:07 +0100 [thread overview]
Message-ID: <20200206104710.16077-1-eric.auger@redhat.com> (raw)
Add the basic infrastructure needed to test AMD nested SVM.
Also add a first basic vmcall test.
Best regards
Eric
This series can be found at:
https://github.com/eauger/linux/tree/v5.5-amd-svm-v4
History:
v3 -> v4:
- gpr64_regs struct just contains 64b mode GPRs ordered
as in x86_register
- cleanup in run_guest (vm* instructions) and reduce
clubber list.
- add some comments
v2 -> v3:
- Took into account Vitaly's comment:
- added "selftests: KVM: Replace get_gdt/idt_base() by
get_gdt/idt()"
- svm.h now is a copy of arch/x86/include/asm/svm.h
- avoid duplicates
v1 -> v2:
- split into 2 patches
- remove the infrastructure to run low-level sub-tests and only
keep vmmcall's one.
- move struct regs into processor.h
- force vmcb_gpa into rax in run_guest()
Eric Auger (3):
selftests: KVM: Replace get_gdt/idt_base() by get_gdt/idt()
selftests: KVM: AMD Nested test infrastructure
selftests: KVM: SVM: Add vmcall test
tools/testing/selftests/kvm/Makefile | 3 +-
.../selftests/kvm/include/x86_64/processor.h | 28 +-
.../selftests/kvm/include/x86_64/svm.h | 297 ++++++++++++++++++
.../selftests/kvm/include/x86_64/svm_util.h | 38 +++
tools/testing/selftests/kvm/lib/x86_64/svm.c | 161 ++++++++++
tools/testing/selftests/kvm/lib/x86_64/vmx.c | 6 +-
.../selftests/kvm/x86_64/svm_vmcall_test.c | 79 +++++
7 files changed, 604 insertions(+), 8 deletions(-)
create mode 100644 tools/testing/selftests/kvm/include/x86_64/svm.h
create mode 100644 tools/testing/selftests/kvm/include/x86_64/svm_util.h
create mode 100644 tools/testing/selftests/kvm/lib/x86_64/svm.c
create mode 100644 tools/testing/selftests/kvm/x86_64/svm_vmcall_test.c
--
2.20.1
next reply other threads:[~2020-02-06 10:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 10:47 Eric Auger [this message]
2020-02-06 10:47 ` [PATCH v4 1/3] selftests: KVM: Replace get_gdt/idt_base() by get_gdt/idt() Eric Auger
2020-02-06 17:13 ` Wei Huang
2020-02-06 19:17 ` Krish Sadhukhan
2020-02-06 10:47 ` [PATCH v4 2/3] selftests: KVM: AMD Nested test infrastructure Eric Auger
2020-02-06 12:20 ` Vitaly Kuznetsov
2020-02-06 12:27 ` Auger Eric
2020-02-06 22:57 ` Krish Sadhukhan
2020-02-07 9:16 ` Vitaly Kuznetsov
2020-02-07 14:16 ` Auger Eric
2020-02-12 11:38 ` Paolo Bonzini
2020-02-06 10:47 ` [PATCH v4 3/3] selftests: KVM: SVM: Add vmcall test Eric Auger
2020-02-06 17:39 ` Wei Huang
2020-02-06 19:08 ` Krish Sadhukhan
2020-02-07 10:05 ` Auger Eric
2020-02-07 10:15 ` Auger Eric
2020-02-12 11:43 ` Paolo Bonzini
2020-02-06 22:46 ` Krish Sadhukhan
2020-02-07 14:06 ` Auger Eric
2020-02-12 11:45 ` Paolo Bonzini
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=20200206104710.16077-1-eric.auger@redhat.com \
--to=eric.auger@redhat.com \
--cc=drjones@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=thuth@redhat.com \
--cc=vkuznets@redhat.com \
--cc=wei.huang2@amd.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;
as well as URLs for NNTP newsgroup(s).