From: Fea Wang <fea.wang@sifive.com>
To: qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Subject: Re: [PATCH v2 0/5] target/riscv: Support RISC-V privilege 1.13 spec
Date: Wed, 15 May 2024 15:56:24 +0800 [thread overview]
Message-ID: <CAKhCfseSAZmg++fW6TbZfFXP80HXs5A-XY7OS2HTTSUzt-7woA@mail.gmail.com> (raw)
In-Reply-To: <20240515075340.2675136-1-fea.wang@sifive.com>
[-- Attachment #1: Type: text/plain, Size: 2014 bytes --]
Sorry that I only put the patch version on the cover letter.
I will resend the patches.
Sincerely,
Fea
Fea.Wang <fea.wang@sifive.com> 於 2024年5月15日 週三 下午3:48寫道:
> Based on the change log for the RISC-V privilege 1.13 spec, add the
> support for ss1p13.
>
> Ref:
> https://github.com/riscv/riscv-isa-manual/blob/a7d93c9/src/priv-preface.adoc?plain=1#L40-L72
>
> Lists what to do without clarification or document format.
> * Redefined misa.MXL to be read-only, making MXLEN a constant.(Skip,
> implementation ignored)
> * Added the constraint that SXLEN≥UXLEN.(Skip, implementation ignored)
> * Defined the misa.V field to reflect that the V extension has been
> implemented.(Skip, existed)
> * Defined the RV32-only medelegh and hedelegh CSRs.(Done in these patches)
> * Defined the misaligned atomicity granule PMA, superseding the proposed
> Zam extension..(Skip, implementation ignored)
> * Allocated interrupt 13 for Sscofpmf LCOFI interrupt.(Skip, existed)
> * Defined hardware error and software check exception codes.(Done in these
> patches)
> * Specified synchronization requirements when changing the PBMTE fields in
> menvcfg and henvcfg.(Skip, implementation ignored)
> * Incorporated Svade and Svadu extension specifications.(Skip, existed)
>
>
> Fea.Wang (4):
> target/riscv: Support the version for ss1p13
> target/riscv: Add 'P1P13' bit in SMSTATEEN0
> target/riscv: Add MEDELEGH, HEDELEGH csrs for RV32
> target/riscv: Reserve exception codes for sw-check and hw-err
>
> Jim Shu (1):
> target/riscv: Reuse the conversion function of priv_spec
>
> target/riscv/cpu.c | 8 ++++++--
> target/riscv/cpu.h | 5 ++++-
> target/riscv/cpu_bits.h | 5 +++++
> target/riscv/cpu_cfg.h | 1 +
> target/riscv/csr.c | 39 ++++++++++++++++++++++++++++++++++++++
> target/riscv/tcg/tcg-cpu.c | 17 ++++++++---------
> 6 files changed, 63 insertions(+), 12 deletions(-)
>
> --
> 2.34.1
>
>
[-- Attachment #2: Type: text/html, Size: 2570 bytes --]
prev parent reply other threads:[~2024-05-15 8:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 7:53 [PATCH v2 0/5] target/riscv: Support RISC-V privilege 1.13 spec Fea.Wang
2024-05-15 7:53 ` [PATCH 1/5] target/riscv: Reuse the conversion function of priv_spec Fea.Wang
2024-05-15 7:53 ` [PATCH 2/5] target/riscv: Support the version for ss1p13 Fea.Wang
2024-05-15 7:53 ` [PATCH 3/5] target/riscv: Add 'P1P13' bit in SMSTATEEN0 Fea.Wang
2024-05-15 7:53 ` [PATCH 4/5] target/riscv: Add MEDELEGH, HEDELEGH csrs for RV32 Fea.Wang
2024-05-15 7:53 ` [PATCH 5/5] target/riscv: Reserve exception codes for sw-check and hw-err Fea.Wang
2024-05-15 7:56 ` Fea Wang [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=CAKhCfseSAZmg++fW6TbZfFXP80HXs5A-XY7OS2HTTSUzt-7woA@mail.gmail.com \
--to=fea.wang@sifive.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.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;
as well as URLs for NNTP newsgroup(s).