From: patchwork-bot+linux-riscv@kernel.org
To: Sean Christopherson <seanjc@google.com>
Cc: linux-riscv@lists.infradead.org, pbonzini@redhat.com,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, ilstam@amazon.com, maz@kernel.org,
oliver.upton@linux.dev, anup@brainfault.org, paul@xen.org
Subject: Re: [PATCH v2 0/2] KVM: Coalesced IO cleanup and test
Date: Tue, 01 Oct 2024 11:35:14 +0000 [thread overview]
Message-ID: <172778251450.314421.17878360494032462055.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240828181446.652474-1-seanjc@google.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Sean Christopherson <seanjc@google.com>:
On Wed, 28 Aug 2024 11:14:44 -0700 you wrote:
> 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.
>
> [...]
Here is the summary with links:
- [v2,1/2] KVM: selftests: Add a test for coalesced MMIO (and PIO on x86)
https://git.kernel.org/riscv/c/215b3cb7a84f
- [v2,2/2] KVM: Clean up coalesced MMIO ring full check
https://git.kernel.org/riscv/c/e027ba1b83ad
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-10-01 11:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 18:14 [PATCH v2 0/2] KVM: Coalesced IO cleanup and test Sean Christopherson
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 [this message]
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=172778251450.314421.17878360494032462055.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--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 \
--cc=seanjc@google.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