From: Andrew Jones <ajones@ventanamicro.com>
To: kvm-riscv@lists.infradead.org
Subject: [PATCH 6/7] RISC-V: KVM: Allow Zbc, Zbk* and Zk* extensions for Guest/VM
Date: Thu, 13 Jul 2023 14:48:30 +0200 [thread overview]
Message-ID: <20230713-bf041a3bbf91d041db3bd623@orel> (raw)
In-Reply-To: <20230712161047.1764756-7-apatel@ventanamicro.com>
On Wed, Jul 12, 2023 at 09:40:46PM +0530, Anup Patel wrote:
> We extend the KVM ISA extension ONE_REG interface to allow KVM
> user space to detect and enable Zbc, Zbk* and Zk* extensions for
> Guest/VM.
>
> Signed-off-by: Anup Patel <apatel@ventanamicro.com>
> ---
> arch/riscv/include/uapi/asm/kvm.h | 11 +++++++++++
> arch/riscv/kvm/vcpu_onereg.c | 22 ++++++++++++++++++++++
> 2 files changed, 33 insertions(+)
>
Reviewed-by: Andrew Jones <ajones@ventanamicro.com>
next prev parent reply other threads:[~2023-07-13 12:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 16:10 [PATCH 0/7] KVM RISC-V ONE_REG ISA extension improvements Anup Patel
2023-07-12 16:10 ` [PATCH 1/7] RISC-V: KVM: Factor-out ONE_REG related code to its own source file Anup Patel
2023-07-13 10:57 ` Andrew Jones
2023-07-12 16:10 ` [PATCH 2/7] RISC-V: KVM: Extend ONE_REG to enable/disable multiple ISA extensions Anup Patel
2023-07-13 11:27 ` Andrew Jones
2023-07-12 16:10 ` [PATCH 3/7] RISC-V: KVM: Allow Zba and Zbs extensions for Guest/VM Anup Patel
2023-07-13 11:32 ` Andrew Jones
2023-07-12 16:10 ` [PATCH 4/7] RISC-V: KVM: Allow Zicntr, Zicsr, Zifencei, and Zihpm " Anup Patel
2023-07-13 11:45 ` Andrew Jones
2023-07-12 16:10 ` [PATCH 5/7] RISC-V: KVM: Sort ISA extensions alphabetically in ONE_REG interface Anup Patel
2023-07-13 11:47 ` Andrew Jones
2023-07-12 16:10 ` [PATCH 6/7] RISC-V: KVM: Allow Zbc, Zbk* and Zk* extensions for Guest/VM Anup Patel
2023-07-13 12:48 ` Andrew Jones [this message]
2023-07-12 16:10 ` [PATCH 7/7] RISC-V: KVM: Allow Zvb* and Zvk* " Anup Patel
2023-07-13 12:49 ` Andrew Jones
2023-07-17 3:54 ` [PATCH 0/7] KVM RISC-V ONE_REG ISA extension improvements Anup Patel
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=20230713-bf041a3bbf91d041db3bd623@orel \
--to=ajones@ventanamicro.com \
--cc=kvm-riscv@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).