From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>
Cc: qemu-riscv@nongnu.org
Subject: [RESEND PATCH 0/1] target/riscv: misa to ISA string conversion fix
Date: Sat, 12 Feb 2022 20:59:09 +0900 [thread overview]
Message-ID: <cover.1644667142.git.research_trasio@irq.a4lg.com> (raw)
S and U are misa bits but not extensions. Thus, they should not be
copied to the ISA string.
I am truly surprised that this patchset is the THIRD attempt to fix this
longstanding problem.
(1) August 2019: by Palmer Dabbelt
<https://lists.nongnu.org/archive/html/qemu-riscv/2019-08/msg00165.html>
<https://lists.nongnu.org/archive/html/qemu-riscv/2019-08/msg00141.html>
<https://lists.nongnu.org/archive/html/qemu-riscv/2019-08/msg00259.html>
(2) April 2021: by Emmanuel Blot
<https://lists.nongnu.org/archive/html/qemu-riscv/2021-04/msg00248.html>
(3) February 2022: by me (this patchset)
I feel this is urgent to eliminate this bug now considering it required
a workaround to RISC-V Linux kernel as I pointed out:
<http://lists.infradead.org/pipermail/linux-riscv/2022-February/012252.html>
Though my patchset is first developed independently, this submitted
version is influenced by (2) Emmanuel Blot's patchset. Thanks to this,
constant "[n]" can now be variable "[]".
It also fixes an ordering issue where 'C' should be preceded by 'L'
(order: 'L' -> 'C') as per the RISC-V ISA Manual (version 20191213),
Table 27.1.
It clarifies the role of `riscv_exts'. It's a single-letter extrension
ordering list.
Tsukasa OI (1):
target/riscv: misa to ISA string conversion fix
target/riscv/cpu.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
base-commit: 0a301624c2f4ced3331ffd5bce85b4274fe132af
--
2.32.0
next reply other threads:[~2022-02-12 11:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 11:59 Tsukasa OI [this message]
2022-02-12 11:59 ` [RESEND PATCH 1/1] target/riscv: misa to ISA string conversion fix Tsukasa OI
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=cover.1644667142.git.research_trasio@irq.a4lg.com \
--to=research_trasio@irq.a4lg.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.