From: Paul Walmsley <paul.walmsley@sifive.com>
To: Palmer Dabbelt <palmer@sifive.com>
Cc: Alistair Francis <Alistair.Francis@wdc.com>,
qemu-riscv@nongnu.org, qemu-devel@nongnu.org,
Atish Patra <Atish.Patra@wdc.com>
Subject: Re: [Qemu-devel] [PATCH for 4.1] RISC-V: Ignore the S and U extensions when formatting ISA strings
Date: Wed, 7 Aug 2019 08:27:30 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1908070804400.13971@viisi.sifive.com> (raw)
In-Reply-To: <20190807145939.1281-1-palmer@sifive.com>
On Wed, 7 Aug 2019, Palmer Dabbelt wrote:
> The ISA strings we're providing from QEMU aren't actually legal RISC-V
> ISA strings, as both the S and U extensions cannot exist as
> single-letter extensions and must instead be multi-letter strings.
> We're still using the ISA strings inside QEMU to track the availiable
> extensions, so this patch just strips out the S and U extensions when
> formatting ISA strings.
>
> This boots Linux on top of 4.1-rc3, which no longer has the U extension
> in /proc/cpuinfo.
>
> Signed-off-by: Palmer Dabbelt <palmer@sifive.com>
> ---
> This is another late one, but I'd like to target it for 4.1 as we're
> providing illegal ISA strings and I don't want to bake that into a bunch
> of other code.
I'm unfamiliar with the underlying QEMU code beyond the patch posted here,
but I can review the intention expressed in the patch description. The
described intent is aligned with Section 22.6 and Table 22.1 of the RISC-V
User-Level ISA Specification version 2.2:
https://github.com/riscv/riscv-isa-manual/blob/master/release/riscv-spec-v2.2.pdf
And on the Linux kernel side we've also recognized that our current
parsing code is handling "s" and "u" incorrectly and that we'll need to
fix it:
https://lore.kernel.org/linux-riscv/alpine.DEB.2.21.9999.1908061818360.13971@viisi.sifive.com/
- Paul
next prev parent reply other threads:[~2019-08-07 15:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 14:59 [Qemu-devel] [PATCH for 4.1] RISC-V: Ignore the S and U extensions when formatting ISA strings Palmer Dabbelt
2019-08-07 15:27 ` Paul Walmsley [this message]
2019-08-07 16:08 ` Peter Maydell
2019-08-07 16:20 ` Palmer Dabbelt
2019-08-07 16:41 ` Peter Maydell
2019-08-07 17:25 ` Palmer Dabbelt
2019-08-07 17:54 ` Alistair Francis
2019-08-13 22:54 ` Palmer Dabbelt
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=alpine.DEB.2.21.9999.1908070804400.13971@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=Alistair.Francis@wdc.com \
--cc=Atish.Patra@wdc.com \
--cc=palmer@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).