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
Subject: Re: [PATCH v2 0/2] riscv: add rv32i,rv32e and rv64e CPUs
Date: Mon, 22 Jan 2024 13:38:54 +1000 [thread overview]
Message-ID: <CAKmqyKP3TMrzyn9SvAzL3Wt9U=4mOPP7F-GOJo5anJn_h1m_2Q@mail.gmail.com> (raw)
In-Reply-To: <20240108161903.353648-1-dbarboza@ventanamicro.com>
On Tue, Jan 9, 2024 at 3:40 AM Daniel Henrique Barboza
<dbarboza@ventanamicro.com> wrote:
>
> Hi,
>
> This is the second version of a buried patch series:
>
> "[PATCH for-9.0 0/6] riscv: rv32i,rv32e,rv64i and rv64e CPUs"
>
> This version shrank to 2 patches since most of the prep work was already
> done by the RVA22 profile implementation, which is now queued in
> riscv-to-apply.next.
>
> The motivation is the same as in v1 - give users a cleaner way of using
> a customized CPU, from scratch, without the need to disable default
> extensions.
>
> Patches based on Alistair's riscv-to-apply.next.
>
> Changes from v1:
> - patches 1 to 4 from v1: dropped
> - patches 5 and 6 from v1: merged into patch 2
> - patch 1 (new):
> - add a new common cpu_init() for all bare CPUs
> - v1 link: https://lore.kernel.org/qemu-riscv/20231113213904.185320-1-dbarboza@ventanamicro.com/
>
>
> Daniel Henrique Barboza (2):
> target/riscv/cpu.c: add riscv_bare_cpu_init()
> target/riscv: add rv32i, rv32e and rv64e CPUs
Do you mind rebasing this on
https://github.com/alistair23/qemu/tree/riscv-to-apply.next ?
Alistai
>
> target/riscv/cpu-qom.h | 3 ++
> target/riscv/cpu.c | 64 ++++++++++++++++++++++++++++++++----------
> 2 files changed, 52 insertions(+), 15 deletions(-)
>
> --
> 2.43.0
>
>
prev parent reply other threads:[~2024-01-22 3:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 16:19 [PATCH v2 0/2] riscv: add rv32i,rv32e and rv64e CPUs Daniel Henrique Barboza
2024-01-08 16:19 ` [PATCH v2 1/2] target/riscv/cpu.c: add riscv_bare_cpu_init() Daniel Henrique Barboza
2024-01-22 3:31 ` Alistair Francis
2024-01-08 16:19 ` [PATCH v2 2/2] target/riscv: add rv32i, rv32e and rv64e CPUs Daniel Henrique Barboza
2024-01-22 3:32 ` Alistair Francis
2024-01-22 3:38 ` 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='CAKmqyKP3TMrzyn9SvAzL3Wt9U=4mOPP7F-GOJo5anJn_h1m_2Q@mail.gmail.com' \
--to=alistair23@gmail.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).