From: Conor Dooley <conor@kernel.org>
To: Tsukasa OI <research_trasio@irq.a4lg.com>
Cc: linux-riscv@lists.infradead.org
Subject: Re: [PATCH 2/2] RISC-V: fix the comment for ISA string workaround
Date: Sat, 22 Jul 2023 11:52:59 +0100 [thread overview]
Message-ID: <20230722-smog-establish-ebb3eaa5e9e9@spud> (raw)
In-Reply-To: <a7d3db75ba6f3bdd6185ff1574c9a71a14a95126.1690006695.git.research_trasio@irq.a4lg.com>
[-- Attachment #1.1: Type: text/plain, Size: 2746 bytes --]
On Sat, Jul 22, 2023 at 06:22:38AM +0000, Tsukasa OI wrote:
> From: Tsukasa OI <research_trasio@irq.a4lg.com>
>
> Extensions prefixed with "Su" won't corrupt the workaround in many
> cases. The only exception is when the first multi-letter extension in the
> ISA string begins with "Su" and is not prefixed with an underscore.
>
> For instance, following ISA string can confuse this QEMU workaround.
>
> * "rv64imacsuclic" (RV64I + M + A + C + "Suclic")
>
> However, this case is very unlikely because extensions prefixed by either
> "Z", "Sm" or "Ss" will most likely precede first.
>
> For instance, the "Suclic" extension (draft as of now) will be placed after
> related "Smclic" and "Ssclic" extensions. It's also highly likely that
> other unprivileged extensions like "Zba" will precede.
>
> It's also possible to suppress the issue in the QEMU workaround with an
> underscore. Following ISA string won't confuse the QEMU workaround.
>
> * "rv64imac_suclic" (RV64I + M + A + C + delimited "Suclic")
>
> This fix is to tell kernel developers the nature of this workaround
> precisely. There are some "Su*" extensions to be ratified but don't worry
> about this workaround too much.
>
> This commit comes with another minor editorial fix.
Which is what?
The new wording is fine by me though..
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
Thanks,
Conor.
> Signed-off-by: Tsukasa OI <research_trasio@irq.a4lg.com>
> ---
> arch/riscv/kernel/cpufeature.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/arch/riscv/kernel/cpufeature.c b/arch/riscv/kernel/cpufeature.c
> index 63277cdc1ea5..91f1ef3e762c 100644
> --- a/arch/riscv/kernel/cpufeature.c
> +++ b/arch/riscv/kernel/cpufeature.c
> @@ -170,10 +170,11 @@ void __init riscv_fill_hwcap(void)
> case 's':
> case 'S':
> /*
> - * Workaround for invalid single-letter 's' & 'u'(QEMU).
> - * No need to set the bit in riscv_isa as 's' & 'u' are
> - * not valid ISA extensions. It works until multi-letter
> - * extension starting with "Su" appears.
> + * Workaround for invalid single-letters 's' & 'u' (QEMU).
> + * No need to set the bits in riscv_isa as 's' and 'u' are
> + * not valid ISA extensions. It works unless the first multi-letter
> + * extension in the ISA string begins with "Su" and not prefixed
> + * with an underscore.
> */
> if (ext[-1] != '_' && tolower(ext[1]) == 'u') {
> ++isa;
> --
> 2.40.0
>
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-07-22 10:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 6:22 [PATCH 0/2] RISC-V: minor fixes to the QEMU workaround in ISA string parser Tsukasa OI
2023-07-22 6:22 ` [PATCH 1/2] RISC-V: make ISA string workaround case-insensitive Tsukasa OI
2023-07-22 10:49 ` Conor Dooley
2023-07-22 6:22 ` [PATCH 2/2] RISC-V: fix the comment for ISA string workaround Tsukasa OI
2023-07-22 10:52 ` Conor Dooley [this message]
2023-07-22 11:22 ` Tsukasa OI
2023-07-22 11:28 ` Conor Dooley
2023-07-26 5:44 ` [PATCH v2 0/1] RISC-V: clarification of the QEMU workaround in the ISA parser Tsukasa OI
2023-07-26 5:44 ` [PATCH v2 1/1] RISC-V: clarify the QEMU workaround in " Tsukasa OI
2023-07-26 6:56 ` Conor Dooley
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=20230722-smog-establish-ebb3eaa5e9e9@spud \
--to=conor@kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=research_trasio@irq.a4lg.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).