From: <wang.yechao255@zte.com.cn>
To: <anup@brainfault.org>, <atish.patra@linux.dev>, <pjw@kernel.org>,
<palmer@dabbelt.com>, <aou@eecs.berkeley.edu>, <alex@ghiti.fr>
Cc: <kvm@vger.kernel.org>, <kvm-riscv@lists.infradead.org>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<wang.yechao255@zte.com.cn>
Subject: [PATCH v2 0/3] RISC-V: KVM: Fix hugepage mapping handling during dirty logging
Date: Wed, 4 Mar 2026 17:21:39 +0800 (CST) [thread overview]
Message-ID: <20260304172139131ChDubMSpGDUB03lY4UCbK@zte.com.cn> (raw)
From: Wang Yechao <wang.yechao255@zte.com.cn>
This series fixes an issue where dirty logging fails to work correctly
with huge pages.
v1 -> v2:
- fix the lost write protection on huge pages
- split huge pages before handling the write protection fault.
- Link to v1:
https://lore.kernel.org/linux-riscv/20260226172245358qVZavIykLL2QC0KoqTO-I@zte.com.cn/T/#u
Wang Yechao (3):
RISC-V: KVM: Fix lost write protection on huge pages during dirty
logging
RISC-V: KVM: Allow splitting huge pages to arbitrary level
RISC-V: KVM: Split huge pages during fault handling for dirty logging
arch/riscv/include/asm/kvm_gstage.h | 4 ++
arch/riscv/kvm/gstage.c | 85 +++++++++++++++++++++++++++--
2 files changed, 85 insertions(+), 4 deletions(-)
--
2.47.3
next reply other threads:[~2026-03-04 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 9:21 wang.yechao255 [this message]
2026-03-04 9:26 ` [PATCH v2 1/3] RISC-V: KVM: Fix lost write protection on huge pages " wang.yechao255
2026-03-06 3:19 ` Nutty.Liu
2026-03-04 9:28 ` [PATCH v2 2/3] RISC-V: KVM: Allow splitting huge pages to arbitrary level wang.yechao255
2026-03-04 9:30 ` [PATCH v2 3/3] RISC-V: KVM: Split huge pages during fault handling for dirty logging wang.yechao255
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=20260304172139131ChDubMSpGDUB03lY4UCbK@zte.com.cn \
--to=wang.yechao255@zte.com.cn \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@linux.dev \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.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
all inboxes | Powered by JetHome®