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 v2 0/2] selftests: KVM: AMD Nested SVM test infrastructure
Date: Mon, 3 Feb 2020 10:08:49 +0100 [thread overview]
Message-ID: <20200203090851.19938-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-v2
History:
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 (2):
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 | 20 +
.../selftests/kvm/include/x86_64/svm.h | 355 ++++++++++++++++++
tools/testing/selftests/kvm/lib/x86_64/svm.c | 211 +++++++++++
.../selftests/kvm/x86_64/svm_vmcall_test.c | 86 +++++
5 files changed, 674 insertions(+), 1 deletion(-)
create mode 100644 tools/testing/selftests/kvm/include/x86_64/svm.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-03 9:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 9:08 Eric Auger [this message]
2020-02-03 9:08 ` [PATCH v2 1/2] selftests: KVM: AMD Nested test infrastructure Eric Auger
2020-02-03 9:39 ` Vitaly Kuznetsov
2020-02-03 9:58 ` Auger Eric
2020-02-03 9:08 ` [PATCH v2 2/2] selftests: KVM: SVM: Add vmcall test Eric Auger
2020-02-03 9:44 ` Vitaly Kuznetsov
2020-02-03 9:59 ` Auger Eric
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=20200203090851.19938-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