From: zhouquan@iscas.ac.cn
To: anup@brainfault.org, ajones@ventanamicro.com,
atishp@atishpatra.org, paul.walmsley@sifive.com,
palmer@dabbelt.com
Cc: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
Quan Zhou <zhouquan@iscas.ac.cn>
Subject: [PATCH 0/2] RISC-V: KVM: Enable ring-based dirty memory tracking
Date: Fri, 13 Jun 2025 19:29:48 +0800 [thread overview]
Message-ID: <cover.1749810735.git.zhouquan@iscas.ac.cn> (raw)
From: Quan Zhou <zhouquan@iscas.ac.cn>
Enable ring-based dirty memory tracking and add some
common KVM tests for riscv.
Quan Zhou (2):
RISC-V: KVM: Enable ring-based dirty memory tracking
KVM: riscv: selftests: Add common supported test cases
Documentation/virt/kvm/api.rst | 2 +-
arch/riscv/include/uapi/asm/kvm.h | 1 +
arch/riscv/kvm/Kconfig | 1 +
arch/riscv/kvm/vcpu.c | 18 ++++++++++++++++--
tools/testing/selftests/kvm/Makefile.kvm | 12 ++++++++++++
.../selftests/kvm/include/riscv/processor.h | 2 ++
tools/testing/selftests/rseq/rseq-riscv.h | 3 +--
7 files changed, 34 insertions(+), 5 deletions(-)
--
2.34.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2025-06-13 11:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 11:29 zhouquan [this message]
2025-06-13 11:29 ` [PATCH 1/2] RISC-V: KVM: Enable ring-based dirty memory tracking zhouquan
2025-07-17 6:10 ` Anup Patel
2025-06-13 11:30 ` [PATCH 2/2] KVM: riscv: selftests: Add common supported test cases zhouquan
2025-06-24 14:10 ` Andrew Jones
2025-07-17 9:24 ` Quan Zhou
2025-07-17 6:12 ` Anup Patel
2025-07-17 9:21 ` Quan Zhou
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=cover.1749810735.git.zhouquan@iscas.ac.cn \
--to=zhouquan@iscas.ac.cn \
--cc=ajones@ventanamicro.com \
--cc=anup@brainfault.org \
--cc=atishp@atishpatra.org \
--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=paul.walmsley@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;
as well as URLs for NNTP newsgroup(s).