From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Sean Christopherson <seanjc@google.com>,
David Woodhouse <dwmw@amazon.co.uk>
Subject: [PATCH v2 0/4] KVM: selftests: xen_shinfo cleanups and slowpath test
Date: Sat, 4 Feb 2023 02:41:47 +0000 [thread overview]
Message-ID: <20230204024151.1373296-1-seanjc@google.com> (raw)
David's new testcase to validate the slow path for EVTCHNOP_send, on top
of cleanups to reduce the amount of copy+paste in the test.
Applies on top of `kvm-x86 selftests`.
David Woodhouse (2):
KVM: selftests: Use enum for test numbers in xen_shinfo_test
KVM: selftests: Add EVTCHNOP_send slow path test to xen_shinfo_test
Sean Christopherson (2):
KVM: selftests: Move the guts of kvm_hypercall() to a separate macro
KVM: selftests: Add helpers to make Xen-style VMCALL/VMMCALL
hypercalls
.../selftests/kvm/include/x86_64/processor.h | 2 +
.../selftests/kvm/lib/x86_64/processor.c | 37 ++-
.../selftests/kvm/x86_64/xen_shinfo_test.c | 221 +++++++++---------
3 files changed, 145 insertions(+), 115 deletions(-)
base-commit: 531f33c5a6edf259da4960de694293e458262d14
--
2.39.1.519.gcb327c4b5f-goog
next reply other threads:[~2023-02-04 2:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 2:41 Sean Christopherson [this message]
2023-02-04 2:41 ` [PATCH v2 1/4] KVM: selftests: Move the guts of kvm_hypercall() to a separate macro Sean Christopherson
2023-02-04 2:41 ` [PATCH v2 2/4] KVM: selftests: Add helpers to make Xen-style VMCALL/VMMCALL hypercalls Sean Christopherson
2023-02-04 2:41 ` [PATCH v2 3/4] KVM: selftests: Use enum for test numbers in xen_shinfo_test Sean Christopherson
2023-02-04 2:41 ` [PATCH v2 4/4] KVM: selftests: Add EVTCHNOP_send slow path test to xen_shinfo_test Sean Christopherson
2023-03-14 13:43 ` [PATCH v2 0/4] KVM: selftests: xen_shinfo cleanups and slowpath test 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=20230204024151.1373296-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=dwmw@amazon.co.uk \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@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
all inboxes | Powered by JetHome®