From: patchwork-bot+linux-riscv@kernel.org
To: Anup Patel <anup@brainfault.org>
Cc: linux-riscv@lists.infradead.org, pbonzini@redhat.com,
palmer@dabbelt.com, pjw@kernel.org,
andrew.jones@oss.qualcomm.com, atish.patra@linux.dev,
kvm-riscv@lists.infradead.org, kvm@vger.kernel.org
Subject: Re: [GIT PULL] KVM/riscv changes for 7.2
Date: Fri, 26 Jun 2026 11:16:32 +0000 [thread overview]
Message-ID: <178247259228.3816447.10031168625434105729.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <CAAhSdy0WTa-jDxg0cQxwqfGM+Det+WxM-ELV3F2ktrcbw8g7Bw@mail.gmail.com>
Hello:
This pull request was applied to riscv/linux.git (for-next)
by Paolo Bonzini <pbonzini@redhat.com>:
On Sun, 14 Jun 2026 15:19:53 +0530 you wrote:
> Hi Paolo,
>
> We have the following KVM RISC-V changes for 7.2:
> 1) Batch G-stage TLB flushes for GPA range based page table updates
> 2) Convert HGEI line management to fully per-HART
> 3) Speed up dirty logging write faults using MMU rwlock and atomic
> PTE updates for permission-only changes
> 4) Use flexible array for APLIC IRQ state
> 5) FWFT fixes for missing CSR dirty marking and stale feature
> exposure to Guest/VM
> 6) Fix logging enable check on a memslot by using
> kvm_slot_dirty_track_enabled()
> 7) Fixes to avoid skipping valid pages in kvm_riscv_gstage_wp_range()
> and kvm_riscv_gstage_unmap_range()
>
> [...]
Here is the summary with links:
- [GIT,PULL] KVM/riscv changes for 7.2
https://git.kernel.org/riscv/c/c6f1b611c66f
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:[~2026-06-26 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-14 9:49 [GIT PULL] KVM/riscv changes for 7.2 Anup Patel
2026-06-26 8:21 ` patchwork-bot+linux-riscv
2026-06-26 11:16 ` 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=178247259228.3816447.10031168625434105729.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=andrew.jones@oss.qualcomm.com \
--cc=anup@brainfault.org \
--cc=atish.patra@linux.dev \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pbonzini@redhat.com \
--cc=pjw@kernel.org \
/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