qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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 v4 0/6] target/riscv: RVA23 profile support
Date: Fri, 31 Jan 2025 10:25:32 +1000	[thread overview]
Message-ID: <CAKmqyKND+dt80wpaePWJRtRcBxUuxtkqPuxRcCRvNwGBZd2_1Q@mail.gmail.com> (raw)
In-Reply-To: <20250115184316.2344583-1-dbarboza@ventanamicro.com>

On Thu, Jan 16, 2025 at 4:44 AM Daniel Henrique Barboza
<dbarboza@ventanamicro.com> wrote:
>
> Hi,
>
> This new version has tweaks suggested by Drew in v3. No major changes
> were made.
>
> Patches based on alistair/riscv-to-apply.next.
>
> All patches acked.
>
> Changes from v3:
> - patch 3:
>   - fix commit msg
>   - drop the 'profile->enabled &&' check from riscv_cpu_check_parent_profile()
> - patch 6:
>   - fix RVA23U64 -> RVA23S64 comment in the profile description
> - v3 link: https://lore.kernel.org/qemu-riscv/20250115134957.2179085-1-dbarboza@ventanamicro.com/
>
> Daniel Henrique Barboza (6):
>   target/riscv: add ssu64xl
>   target/riscv: use RVB in RVA22U64
>   target/riscv: add profile u_parent and s_parent
>   target/riscv: change priv_ver check in validate_profile()
>   target/riscv: add RVA23U64 profile
>   target/riscv: add RVA23S64 profile

Thanks!

Applied to riscv-to-apply.next

Alistair

>
>  target/riscv/cpu-qom.h            |   2 +
>  target/riscv/cpu.c                |  81 ++++++++++++++++++++++++++++--
>  target/riscv/cpu.h                |   3 +-
>  target/riscv/tcg/tcg-cpu.c        |  37 ++++++++++----
>  tests/data/acpi/riscv64/virt/RHCT | Bin 390 -> 400 bytes
>  5 files changed, 109 insertions(+), 14 deletions(-)
>
> --
> 2.47.1
>
>


      parent reply	other threads:[~2025-01-31  0:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-15 18:43 [PATCH v4 0/6] target/riscv: RVA23 profile support Daniel Henrique Barboza
2025-01-15 18:43 ` [PATCH v4 1/6] target/riscv: add ssu64xl Daniel Henrique Barboza
2025-01-30 23:51   ` Alistair Francis
2025-01-15 18:43 ` [PATCH v4 2/6] target/riscv: use RVB in RVA22U64 Daniel Henrique Barboza
2025-01-30 23:52   ` Alistair Francis
2025-01-15 18:43 ` [PATCH v4 3/6] target/riscv: add profile u_parent and s_parent Daniel Henrique Barboza
2025-01-31  0:06   ` Alistair Francis
2025-01-15 18:43 ` [PATCH v4 4/6] target/riscv: change priv_ver check in validate_profile() Daniel Henrique Barboza
2025-01-31  0:07   ` Alistair Francis
2025-01-15 18:43 ` [PATCH v4 5/6] target/riscv: add RVA23U64 profile Daniel Henrique Barboza
2025-01-31  0:09   ` Alistair Francis
2025-01-15 18:43 ` [PATCH v4 6/6] target/riscv: add RVA23S64 profile Daniel Henrique Barboza
2025-01-31  0:13   ` Alistair Francis
2025-01-31  0:25 ` 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=CAKmqyKND+dt80wpaePWJRtRcBxUuxtkqPuxRcCRvNwGBZd2_1Q@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).