All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hongren (Zenithal) Zheng" <i@zenithal.me>
To: Atish Patra <atishp@rivosinc.com>, Palmer Dabbelt <palmer@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RISC-V: cpu.c: remove nonexistent ext from cpuinfo
Date: Wed, 18 May 2022 16:40:18 +0800	[thread overview]
Message-ID: <YoSw8lNHJqRDy6lg@Sun> (raw)
In-Reply-To: <YmcbwYcSzwLSepWZ@Sun>

On Tue, Apr 26, 2022 at 06:08:01AM +0800, Hongren (Zenithal) Zheng wrote:
> There are no single-letter B/K/J extentions,
> as they are never ratified. For P, it is still in
> progress and not ratified.
> 
> The ordering constraint of these placerholders is now removed
> from the spec. By commit ("Delete more nonexistent
> extensions from the naming constraints") of riscv/riscv-isa-manual

Hi, is there any further update on this patch?

> 
> Signed-off-by: Hongren (Zenithal) Zheng <i@zenithal.me>
> ---
>  arch/riscv/kernel/cpu.c | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/arch/riscv/kernel/cpu.c b/arch/riscv/kernel/cpu.c
> index ccb617791e56..53a061ab0743 100644
> --- a/arch/riscv/kernel/cpu.c
> +++ b/arch/riscv/kernel/cpu.c
> @@ -113,10 +113,8 @@ static void print_isa_ext(struct seq_file *f)
>  /*
>   * These are the only valid base (single letter) ISA extensions as per the spec.
>   * It also specifies the canonical order in which it appears in the spec.
> - * Some of the extension may just be a place holder for now (B, K, P, J).
> - * This should be updated once corresponding extensions are ratified.
>   */
> -static const char base_riscv_exts[13] = "imafdqcbkjpvh";
> +static const char base_riscv_exts[9] = "imafdqcvh";

The base_riscv_exts "imafdqcvh" is exactly the spec now, as
https://github.com/riscv/riscv-isa-manual/commit/db7a4a0dad0e99d1ec1fc67b582624fc0aeae98e
(Add single-letter "H" extension to the table)
has shown

>  
>  static void print_isa(struct seq_file *f, const char *isa)
>  {
> -- 
> 2.35.1
> 

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: "Hongren (Zenithal) Zheng" <i@zenithal.me>
To: Atish Patra <atishp@rivosinc.com>, Palmer Dabbelt <palmer@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RISC-V: cpu.c: remove nonexistent ext from cpuinfo
Date: Wed, 18 May 2022 16:40:18 +0800	[thread overview]
Message-ID: <YoSw8lNHJqRDy6lg@Sun> (raw)
In-Reply-To: <YmcbwYcSzwLSepWZ@Sun>

On Tue, Apr 26, 2022 at 06:08:01AM +0800, Hongren (Zenithal) Zheng wrote:
> There are no single-letter B/K/J extentions,
> as they are never ratified. For P, it is still in
> progress and not ratified.
> 
> The ordering constraint of these placerholders is now removed
> from the spec. By commit ("Delete more nonexistent
> extensions from the naming constraints") of riscv/riscv-isa-manual

Hi, is there any further update on this patch?

> 
> Signed-off-by: Hongren (Zenithal) Zheng <i@zenithal.me>
> ---
>  arch/riscv/kernel/cpu.c | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/arch/riscv/kernel/cpu.c b/arch/riscv/kernel/cpu.c
> index ccb617791e56..53a061ab0743 100644
> --- a/arch/riscv/kernel/cpu.c
> +++ b/arch/riscv/kernel/cpu.c
> @@ -113,10 +113,8 @@ static void print_isa_ext(struct seq_file *f)
>  /*
>   * These are the only valid base (single letter) ISA extensions as per the spec.
>   * It also specifies the canonical order in which it appears in the spec.
> - * Some of the extension may just be a place holder for now (B, K, P, J).
> - * This should be updated once corresponding extensions are ratified.
>   */
> -static const char base_riscv_exts[13] = "imafdqcbkjpvh";
> +static const char base_riscv_exts[9] = "imafdqcvh";

The base_riscv_exts "imafdqcvh" is exactly the spec now, as
https://github.com/riscv/riscv-isa-manual/commit/db7a4a0dad0e99d1ec1fc67b582624fc0aeae98e
(Add single-letter "H" extension to the table)
has shown

>  
>  static void print_isa(struct seq_file *f, const char *isa)
>  {
> -- 
> 2.35.1
> 

  reply	other threads:[~2022-05-18  8:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25 22:08 [PATCH] RISC-V: cpu.c: remove nonexistent ext from cpuinfo Hongren (Zenithal) Zheng
2022-04-25 22:08 ` Hongren (Zenithal) Zheng
2022-05-18  8:40 ` Hongren (Zenithal) Zheng [this message]
2022-05-18  8:40   ` Hongren (Zenithal) Zheng
2022-06-02  3:52   ` Palmer Dabbelt
2022-06-02  3:52     ` Palmer Dabbelt
2022-06-12 18:20     ` Hongren Zheng
2022-06-12 18:20       ` Hongren Zheng
2023-03-16 12:54       ` Hongren Zheng
2023-03-16 12:54         ` Hongren Zheng

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=YoSw8lNHJqRDy6lg@Sun \
    --to=i@zenithal.me \
    --cc=atishp@rivosinc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@rivosinc.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 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.