From: Alistair Francis <alistair23@gmail.com>
To: Ian Brockbank <Ian.Brockbank@cirrus.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
Palmer Dabbelt <palmer@dabbelt.com>,
Alistair Francis <alistair.francis@wdc.com>,
Bin Meng <bmeng.cn@gmail.com>, Weiwei Li <liwei1518@gmail.com>,
Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
Liu Zhiwei <zhiwei_liu@linux.alibaba.com>
Subject: Re: [PATCH 00/11 v2] RISC-V: support CLIC v0.9 specification
Date: Fri, 6 Sep 2024 13:56:40 +1000 [thread overview]
Message-ID: <CAKmqyKMBsOh4kc1_PDnTocMAGKB2OBMwLLZnVByWuOW9MtMc1Q@mail.gmail.com> (raw)
In-Reply-To: <20240819160742.27586-1-Ian.Brockbank@cirrus.com>
On Tue, Aug 20, 2024 at 2:08 AM Ian Brockbank <Ian.Brockbank@cirrus.com> wrote:
>
> [Resubmission now the merge is correct]
>
> This patch set gives an implementation of "RISC-V Core-Local Interrupt
> Controller(CLIC) Version 0.9-draft-20210217". It comes from [1], where
> you can find the pdf format or the source code.
Thanks for the patches!
I left some comments on the cover letter and throughout the series.
The main points are that we need to support a release spec (draft is
ok, but it needs to be tagged as a version). On top of that we want to
try and keep the CSR changes in target/riscv. We don't want to be
including the hw/intc code all over the place. time_helper.c for
example is how the ACLINT works, where we try to keep as much of the
CPU code in target/riscv.
Also we will need extension checks for all of the relevant CLIC
extensions. Guest code should not notice any changes after this series
unless they enable the CLIC extensions.
Alistair
>
> This is based on the implementation from 2021 by Liu Zhiwei [3], who took
> over the job from Michael Clark, who gave the first implementation of
> clic-v0.7 specification [2]. I believe this implementation addresses all
> the comments in Liu Zhiwei's RFC patch thread.
>
> This implementation follows the CLIC 0.9-stable draft at 14 March 2024,
> with the following exceptions and implementation details:
> - the CLIC control registers are memory-mapped as per earlier drafts (in
> particular version 0.9-draft, 20 June 2023)
> - the indirect CSR control in 0.9-stable is not implemented
> - the vector table can be either handler addresses (as per the spec)
> or a jump table where each entry is processed as an instruction,
> selectable with version number v0.9-jmp
> - each hart is assigned its own CLIC block
> - if PRV_S and/or PRV_M are supported, they are currently assumed to follow
> the PRV_M registers; a subsequent update will address this
> - support for PRV_S and PRV_M is selectable at CLIC instantiation
> - PRV_S and PRV_U registers are currently separate from PRV_M; a subsequent
> update will turn them into filtered views onto the PRV_M registers
> - each hart is assigned its own CLIC block
> - support for PRV_S and PRV_M is selectable at CLIC instantiation by
> passing in a base address for the given modes; a base address of 0 is
> treated as not supported
> - PRV_S and PRV_U registers are mapped onto the PRV_M controls with
> appropriate filtering for the access mode
> - the RISCV virt machine has been updated to allow CLIC emulation by
> passing "machine=virt,clic=on" on the command line; various other
> parameters have been added to allow finer control of the CLIC behavior
>
> The implementation (in jump-table mode) has been verified to match the
> Cirrus Logic silicon (PRV_M only), which is based upon the Pulp
> implementation [4] as of June 2023.
>
> The implementation also includes a selection of qtests designed to verify
> operation in all possible combinations of PRV_M, PRV_S and PRV_U.
>
> [1] specification website: https://github.com/riscv/riscv-fast-interrupt.
> [2] Michael Clark origin work:
> https://github.com/sifive/riscv-qemu/tree/sifive-clic.
> [3] RFC Patch submission by Liu Zhiwei:
> https://lists.gnu.org/archive/html/qemu-devel/2021-04/msg01417.html
> [4] Pulp implementation of CLIC: https://github.com/pulp-platform/clic
>
> Ian Brockbank (11):
> target/riscv: Add CLIC CSR mintstatus
> target/riscv: Update CSR xintthresh in CLIC mode
> hw/intc: Add CLIC device
> target/riscv: Update CSR xie in CLIC mode
> target/riscv: Update CSR xip in CLIC mode
> target/riscv: Update CSR xtvec in CLIC mode
> target/riscv: Update CSR xnxti in CLIC mode
> target/riscv: Update interrupt handling in CLIC mode
> target/riscv: Update interrupt return in CLIC mode
> hw/riscv: add CLIC into virt machine
> tests: add riscv clic qtest case and a function in qtest
>
> This message and any attachments may contain privileged and confidential information that is intended solely for the person(s) to whom it is addressed. If you are not an intended recipient you must not: read; copy; distribute; discuss; take any action in or make any reliance upon the contents of this message; nor open or read any attachment. If you have received this message in error, please notify us as soon as possible on the following telephone number and destroy this message including any attachments. Thank you. Cirrus Logic International (UK) Ltd and Cirrus Logic International Semiconductor Ltd are companies registered in Scotland, with registered numbers SC089839 and SC495735 respectively. Our registered office is at 7B Nightingale Way, Quartermile, Edinburgh, EH3 9EG, UK. Tel: +44 (0)131 272 7000. www.cirrus.com
>
prev parent reply other threads:[~2024-09-06 3:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <https://lists.gnu.org/archive/html/qemu-riscv/2024-08/msg00234.html>
2024-08-14 8:27 ` [PATCH 00/11] RISC-V: support CLIC v0.9 specification Ian Brockbank
2024-08-14 8:27 ` [PATCH 03/11] hw/intc: Add CLIC device Ian Brockbank
2024-08-14 8:27 ` [PATCH 02/11] target/riscv: Update CSR xintthresh in CLIC mode Ian Brockbank
2024-08-14 8:27 ` [PATCH 01/11] target/riscv: Add CLIC CSR mintstatus Ian Brockbank
2024-08-14 8:27 ` [PATCH 04/11] target/riscv: Update CSR xie in CLIC mode Ian Brockbank
2024-08-14 8:27 ` [PATCH 05/11] target/riscv: Update CSR xip " Ian Brockbank
2024-08-14 8:27 ` [PATCH 07/11] target/riscv: Update CSR xnxti " Ian Brockbank
2024-08-14 8:27 ` [PATCH 06/11] target/riscv: Update CSR xtvec " Ian Brockbank
2024-08-14 14:11 ` [PATCH 00/11] RISC-V: support CLIC v0.9 specification Ian Brockbank
2024-08-19 16:02 ` [PATCH 00/11 v2] " Ian Brockbank
2024-08-19 16:02 ` [PATCH 01/11 v2] target/riscv: Add CLIC CSR mintstatus Ian Brockbank
2024-09-06 2:44 ` Alistair Francis
2024-09-06 3:04 ` Alistair Francis
2024-08-19 16:02 ` [PATCH 02/11 v2] target/riscv: Update CSR xintthresh in CLIC mode Ian Brockbank
2024-09-06 2:52 ` Alistair Francis
2024-08-19 16:02 ` [PATCH 03/11 v2] hw/intc: Add CLIC device Ian Brockbank
2024-08-19 16:02 ` [PATCH 04/11 v2] target/riscv: Update CSR xie in CLIC mode Ian Brockbank
2024-09-06 2:58 ` Alistair Francis
2024-09-06 3:20 ` Alistair Francis
2024-08-19 16:02 ` [PATCH 05/11 v2] target/riscv: Update CSR xip " Ian Brockbank
2024-08-19 16:02 ` [PATCH 06/11 v2] target/riscv: Update CSR xtvec " Ian Brockbank
2024-09-06 3:02 ` Alistair Francis
2024-08-19 16:02 ` [PATCH 07/11 v2] target/riscv: Update CSR xnxti " Ian Brockbank
2024-08-19 16:02 ` [PATCH 08/11 v2] target/riscv: Update interrupt handling " Ian Brockbank
2024-09-06 3:49 ` Alistair Francis
2024-08-19 16:02 ` [PATCH 09/11 v2] target/riscv: Update interrupt return " Ian Brockbank
2024-08-19 16:02 ` [PATCH 10/11 v2] hw/riscv: add CLIC into virt machine Ian Brockbank
2024-08-19 16:02 ` [PATCH 11/11 v2] tests: add riscv clic qtest case and a function in qtest Ian Brockbank
2024-09-06 3:52 ` Alistair Francis
2024-09-04 7:57 ` [PATCH 00/11 v2] RISC-V: support CLIC v0.9 specification Ian Brockbank
2024-09-06 2:48 ` Alistair Francis
2024-09-06 3:56 ` 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=CAKmqyKMBsOh4kc1_PDnTocMAGKB2OBMwLLZnVByWuOW9MtMc1Q@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=Ian.Brockbank@cirrus.com \
--cc=alistair.francis@wdc.com \
--cc=bmeng.cn@gmail.com \
--cc=dbarboza@ventanamicro.com \
--cc=liwei1518@gmail.com \
--cc=palmer@dabbelt.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).