From: patchwork-bot+linux-riscv@kernel.org
To: Jinyu Tang <tjytimi@163.com>
Cc: linux-riscv@lists.infradead.org, apatel@ventanamicro.com,
anup@brainfault.org, pbonzini@redhat.com, seanjc@google.com,
kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, atish.patra@linux.dev,
pjw@kernel.org, paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr,
radim.krcmar@oss.qualcomm.com, andrew.jones@oss.qualcomm.com,
conor.dooley@microchip.com, yongxuan.wang@sifive.com,
nutty.liu@hotmail.com
Subject: Re: [PATCH 0/5] KVM: riscv: Speed up dirty logging write faults
Date: Fri, 26 Jun 2026 08:21:20 +0000 [thread overview]
Message-ID: <178246208080.3816447.14235715613320602429.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260517153427.94889-1-tjytimi@163.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Anup Patel <anup@brainfault.org>:
On Sun, 17 May 2026 23:34:22 +0800 you wrote:
> This series speeds up the common dirty logging write fault path for
> RISC-V KVM.
>
> When dirty logging is enabled, guest writes to write-protected G-stage
> 4K leaves currently go through the full fault path and take mmu_lock for
> write. That is expensive once the leaf already exists and
> only needs its permission and dirty state updated.
>
> [...]
Here is the summary with links:
- [1/5] KVM: riscv: Rely on common MMU notifier locking
(no matching commit)
- [2/5] KVM: riscv: Use an rwlock for mmu_lock
(no matching commit)
- [3/5] KVM: riscv: Add a G-stage PTE cmpxchg helper
https://git.kernel.org/riscv/c/7dd416fdd3fb
- [4/5] KVM: riscv: Update G-stage PTE permissions atomically
https://git.kernel.org/riscv/c/d7a26a0ba715
- [5/5] KVM: riscv: Fast-path dirty logging write faults
https://git.kernel.org/riscv/c/7705be59eb2d
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 8:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-17 15:34 Jinyu Tang
2026-05-17 15:34 ` [PATCH 1/5] KVM: riscv: Rely on common MMU notifier locking Jinyu Tang
2026-05-17 15:34 ` [PATCH 2/5] KVM: riscv: Use an rwlock for mmu_lock Jinyu Tang
2026-05-17 15:34 ` [PATCH 3/5] KVM: riscv: Add a G-stage PTE cmpxchg helper Jinyu Tang
2026-05-17 15:34 ` [PATCH 4/5] KVM: riscv: Update G-stage PTE permissions atomically Jinyu Tang
2026-05-17 15:34 ` [PATCH 5/5] KVM: riscv: Fast-path dirty logging write faults Jinyu Tang
2026-05-28 22:35 ` Inochi Amaoto
2026-06-03 13:12 ` [PATCH 0/5] KVM: riscv: Speed up " Anup Patel
2026-06-26 8:21 ` 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=178246208080.3816447.14235715613320602429.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alex@ghiti.fr \
--cc=andrew.jones@oss.qualcomm.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=atish.patra@linux.dev \
--cc=conor.dooley@microchip.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nutty.liu@hotmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pbonzini@redhat.com \
--cc=pjw@kernel.org \
--cc=radim.krcmar@oss.qualcomm.com \
--cc=seanjc@google.com \
--cc=tjytimi@163.com \
--cc=yongxuan.wang@sifive.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®