From: Anup Patel <apatel@ventanamicro.com>
To: Will Deacon <will@kernel.org>,
julien.thierry.kdev@gmail.com, maz@kernel.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Atish Patra <atishp@atishpatra.org>,
Andrew Jones <ajones@ventanamicro.com>,
Anup Patel <anup@brainfault.org>,
kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
Anup Patel <apatel@ventanamicro.com>
Subject: [kvmtool PATCH 00/10] More ISA extensions
Date: Wed, 14 Feb 2024 17:51:31 +0530 [thread overview]
Message-ID: <20240214122141.305126-1-apatel@ventanamicro.com> (raw)
This series adds support more ISA extensions namely: Zbc, scalar crypto,
vector crypto, Zfh[min], Zihintntl, Zvfh[min], and Zfa. The series also
adds a command-line option to disable SBI STA extension for Guest/VM.
These patches can also be found in the riscv_more_exts_v1 branch at:
https://github.com/avpatel/kvmtool.git
Anup Patel (10):
Sync-up header with Linux-6.8-rc4 for KVM RISC-V
kvmtool: Fix absence of __packed definition
riscv: Add Zbc extension support
riscv: Add scalar crypto extensions support
riscv: Add vector crypto extensions support
riscv: Add Zfh[min] extensions support
riscv: Add Zihintntl extension support
riscv: Add Zvfh[min] extensions support
riscv: Add Zfa extensiona support
riscv: Allow disabling SBI STA extension for Guest
include/kvm/compiler.h | 2 +
include/linux/kvm.h | 140 ++++++++++------------------
include/linux/virtio_config.h | 8 +-
include/linux/virtio_pci.h | 68 ++++++++++++++
riscv/fdt.c | 27 ++++++
riscv/include/asm/kvm.h | 40 ++++++++
riscv/include/kvm/csr.h | 15 +++
riscv/include/kvm/kvm-config-arch.h | 86 ++++++++++++++++-
riscv/kvm-cpu.c | 31 ++++++
x86/include/asm/kvm.h | 3 +
10 files changed, 328 insertions(+), 92 deletions(-)
create mode 100644 riscv/include/kvm/csr.h
--
2.34.1
next reply other threads:[~2024-02-14 12:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 12:21 Anup Patel [this message]
2024-02-14 12:21 ` [kvmtool PATCH 01/10] Sync-up header with Linux-6.8-rc4 for KVM RISC-V Anup Patel
2024-02-14 12:21 ` [kvmtool PATCH 02/10] kvmtool: Fix absence of __packed definition Anup Patel
2024-02-14 12:21 ` [kvmtool PATCH 03/10] riscv: Add Zbc extension support Anup Patel
2024-03-05 13:35 ` Andrew Jones
2024-02-14 12:21 ` [kvmtool PATCH 04/10] riscv: Add scalar crypto extensions support Anup Patel
2024-03-05 13:48 ` Andrew Jones
2024-03-25 15:32 ` Anup Patel
2024-02-14 12:21 ` [kvmtool PATCH 05/10] riscv: Add vector " Anup Patel
2024-03-05 13:49 ` Andrew Jones
2024-02-14 12:21 ` [kvmtool PATCH 06/10] riscv: Add Zfh[min] " Anup Patel
2024-03-05 13:49 ` Andrew Jones
2024-02-14 12:21 ` [kvmtool PATCH 07/10] riscv: Add Zihintntl extension support Anup Patel
2024-03-05 13:50 ` Andrew Jones
2024-02-14 12:21 ` [kvmtool PATCH 08/10] riscv: Add Zvfh[min] extensions support Anup Patel
2024-03-05 13:51 ` Andrew Jones
2024-02-14 12:21 ` [kvmtool PATCH 09/10] riscv: Add Zfa extensiona support Anup Patel
2024-03-05 13:51 ` Andrew Jones
2024-02-14 12:21 ` [kvmtool PATCH 10/10] riscv: Allow disabling SBI STA extension for Guest Anup Patel
2024-03-05 13:52 ` 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=20240214122141.305126-1-apatel@ventanamicro.com \
--to=apatel@ventanamicro.com \
--cc=ajones@ventanamicro.com \
--cc=anup@brainfault.org \
--cc=atishp@atishpatra.org \
--cc=julien.thierry.kdev@gmail.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=will@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