From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>
Cc: kvm@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, Ilias Stamatis <ilstam@amazon.com>,
Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
Anup Patel <anup@brainfault.org>,
Sean Christopherson <seanjc@google.com>,
Paul Durrant <paul@xen.org>
Subject: [PATCH v2 0/2] KVM: Coalesced IO cleanup and test
Date: Wed, 28 Aug 2024 11:14:44 -0700 [thread overview]
Message-ID: <20240828181446.652474-1-seanjc@google.com> (raw)
Add a regression test for the bug fixed by commit 92f6d4130497 ("KVM:
Fix coalesced_mmio_has_room() to avoid premature userspace exit"), and
then do additional clean up on the offending KVM code. I wrote the test
mainly so that I was confident I actually understood Ilias' fix.
This applies on the aforementioned commit, which is sitting in
kvm-x86/generic.
Fully tested on x86 and arm64, compile tested on RISC-V.
Ilias, I deliberately didn't include your Reviewed-by for the selftest, just
in case I botched something during the (minor, in theory) rework.
v2:
- Collect a review. [Ilias]
- Fix a typo in patch 2's changelog. [Ilias]
- Rework the selftest to containerize the coalesced I/O ring and its state,
to hopefully make it easier to extend the test to validate using a ring
other than KVM's built-in default. [Ilias]
Sean Christopherson (2):
KVM: selftests: Add a test for coalesced MMIO (and PIO on x86)
KVM: Clean up coalesced MMIO ring full check
tools/testing/selftests/kvm/Makefile | 3 +
.../testing/selftests/kvm/coalesced_io_test.c | 236 ++++++++++++++++++
.../testing/selftests/kvm/include/kvm_util.h | 26 ++
virt/kvm/coalesced_mmio.c | 29 +--
4 files changed, 273 insertions(+), 21 deletions(-)
create mode 100644 tools/testing/selftests/kvm/coalesced_io_test.c
base-commit: 728d17c2cb8cc5f9ac899173d0e9a67fb8887622
--
2.46.0.295.g3b9ea8a38a-goog
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2024-08-28 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 18:14 Sean Christopherson [this message]
2024-08-28 18:14 ` [PATCH v2 1/2] KVM: selftests: Add a test for coalesced MMIO (and PIO on x86) Sean Christopherson
2024-08-28 18:14 ` [PATCH v2 2/2] KVM: Clean up coalesced MMIO ring full check Sean Christopherson
2024-08-31 0:20 ` [PATCH v2 0/2] KVM: Coalesced IO cleanup and test Sean Christopherson
2024-10-01 11:35 ` patchwork-bot+linux-riscv
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=20240828181446.652474-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=ilstam@amazon.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=paul@xen.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