From: Alistair Francis <alistair23@gmail.com>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
alistair.francis@wdc.com, bmeng@tinylab.org,
liwei1518@gmail.com, zhiwei_liu@linux.alibaba.com,
palmer@rivosinc.com, ajones@ventanamicro.com
Subject: Re: [PATCH v2 0/3] target/riscv/kvm: update to Linux 6.14-rc3
Date: Mon, 24 Feb 2025 11:31:52 +1000 [thread overview]
Message-ID: <CAKmqyKPaCJq87mAdOscatcWq=8zKAdy35TY8+WLDMoV=1_=eaQ@mail.gmail.com> (raw)
In-Reply-To: <20250221141834.626722-1-dbarboza@ventanamicro.com>
On Sat, Feb 22, 2025 at 12:19 AM Daniel Henrique Barboza
<dbarboza@ventanamicro.com> wrote:
>
> Hi,
>
> In this version all changes were made in patch 2. In the first posting I
> forgot to update how riscv,isa was going to be calculated when
> ext_ziccrse is set by KVM.
>
> A change was made in isa_edata_arr[] to use ext_ziccrse, instead of
> 'has_priv_1_11', and TCG code were changed to set ext_ziccrse
> accordingly.
>
> No other changes made. Patches based on alistair/riscv-to-apply.next.
>
> Changes from v1:
> - patch 2:
> - use 'ext_ziccrse' instead of 'has_priv_1_11' in isa_edata_arr[]
> - v1 link: https://lore.kernel.org/qemu-riscv/20250218163854.425607-1-dbarboza@ventanamicro.com/
>
> Daniel Henrique Barboza (3):
> linux-headers: Update to Linux v6.14-rc3
> target/riscv/cpu.c: create flag for ziccrse
> target/riscv/kvm: add extensions after 6.14-rc3 update
Thanks!
Applied to riscv-to-apply.next
Alistair
>
> include/standard-headers/linux/ethtool.h | 4 +
> include/standard-headers/linux/fuse.h | 76 ++++++++++++++++++-
> .../linux/input-event-codes.h | 1 +
> include/standard-headers/linux/pci_regs.h | 16 ++--
> include/standard-headers/linux/virtio_pci.h | 14 ++++
> linux-headers/asm-arm64/kvm.h | 3 -
> linux-headers/asm-loongarch/kvm_para.h | 1 +
> linux-headers/asm-riscv/kvm.h | 7 +-
> linux-headers/asm-x86/kvm.h | 1 +
> linux-headers/linux/iommufd.h | 35 ++++++---
> linux-headers/linux/kvm.h | 8 +-
> linux-headers/linux/stddef.h | 13 +++-
> linux-headers/linux/vduse.h | 2 +-
> target/riscv/cpu.c | 3 +-
> target/riscv/cpu_cfg.h | 3 +
> target/riscv/kvm/kvm-cpu.c | 3 +
> target/riscv/tcg/tcg-cpu.c | 2 +
> 17 files changed, 156 insertions(+), 36 deletions(-)
>
> --
> 2.48.1
>
>
prev parent reply other threads:[~2025-02-24 1:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 14:18 [PATCH v2 0/3] target/riscv/kvm: update to Linux 6.14-rc3 Daniel Henrique Barboza
2025-02-21 14:18 ` [PATCH v2 1/3] linux-headers: Update to Linux v6.14-rc3 Daniel Henrique Barboza
2025-02-21 14:18 ` [PATCH v2 2/3] target/riscv/cpu.c: create flag for ziccrse Daniel Henrique Barboza
2025-02-21 15:11 ` Andrew Jones
2025-02-21 14:18 ` [PATCH v2 3/3] target/riscv/kvm: add extensions after 6.14-rc3 update Daniel Henrique Barboza
2025-02-24 1:31 ` Alistair Francis [this message]
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='CAKmqyKPaCJq87mAdOscatcWq=8zKAdy35TY8+WLDMoV=1_=eaQ@mail.gmail.com' \
--to=alistair23@gmail.com \
--cc=ajones@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=bmeng@tinylab.org \
--cc=dbarboza@ventanamicro.com \
--cc=liwei1518@gmail.com \
--cc=palmer@rivosinc.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.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).