From: zhouquan@iscas.ac.cn
To: anup@brainfault.org, ajones@ventanamicro.com,
atishp@atishpatra.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu
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/4] RISC-V: KVM: Allow Svvptc/Zabha/Ziccrse exts for guests
Date: Thu, 28 Nov 2024 11:20:53 +0800 [thread overview]
Message-ID: <cover.1732762121.git.zhouquan@iscas.ac.cn> (raw)
From: Quan Zhou <zhouquan@iscas.ac.cn>
Advertise Svvptc/Zabha/Ziccrse extensions to KVM guest
when underlying host supports it.
Quan Zhou (4):
RISC-V: KVM: Allow Svvptc extension for Guest/VM
RISC-V: KVM: Allow Zabha extension for Guest/VM
RISC-V: KVM: Allow Ziccrse extension for Guest/VM
KVM: riscv: selftests: Add Svvptc/Zabha/Ziccrse exts to get-reg-list
test
arch/riscv/include/uapi/asm/kvm.h | 3 +++
arch/riscv/kvm/vcpu_onereg.c | 6 ++++++
tools/testing/selftests/kvm/riscv/get-reg-list.c | 12 ++++++++++++
3 files changed, 21 insertions(+)
--
2.34.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2024-11-28 3:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 3:20 zhouquan [this message]
2024-11-28 3:21 ` [PATCH 1/4] RISC-V: KVM: Allow Svvptc extension for Guest/VM zhouquan
2024-11-28 8:50 ` Andrew Jones
2024-11-28 3:21 ` [PATCH 2/4] RISC-V: KVM: Allow Zabha " zhouquan
2024-11-28 8:52 ` Andrew Jones
2024-11-28 3:22 ` [PATCH 3/4] RISC-V: KVM: Allow Ziccrse " zhouquan
2024-11-28 8:54 ` Andrew Jones
2024-11-28 3:22 ` [PATCH 4/4] KVM: riscv: selftests: Add Svvptc/Zabha/Ziccrse exts to get-reg-list test zhouquan
2024-11-28 9:00 ` Andrew Jones
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.1732762121.git.zhouquan@iscas.ac.cn \
--to=zhouquan@iscas.ac.cn \
--cc=ajones@ventanamicro.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--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).