From: Andrew Jones <ajones@ventanamicro.com>
To: Sunil V L <sunilvl@ventanamicro.com>
Cc: util-linux@vger.kernel.org,
"Anup Patel" <apatel@ventanamicro.com>,
"Conor Dooley" <conor@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Alexandre Ghiti" <alexghiti@rivosinc.com>,
"Samuel Holland" <samuel.holland@sifive.com>,
"Björn Töpel" <bjorn@kernel.org>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Atish Patra" <atishp@rivosinc.com>,
"Karel Zak" <kzak@redhat.com>
Subject: Re: [PATCH v2] lscpu: RISC-V: Print ISA information in summary
Date: Tue, 11 Mar 2025 17:19:52 +0100 [thread overview]
Message-ID: <20250311-8617d8509ac9d1ed6a3dbc82@orel> (raw)
In-Reply-To: <20250311160646.1257131-1-sunilvl@ventanamicro.com>
On Tue, Mar 11, 2025 at 09:36:46PM +0530, Sunil V L wrote:
> The ISA information for RISC-V is important for understanding the
> different extensions supported by the CPU. Print the ISA information in
> the summary, with the Base ISA and single-letter extensions at the
> beginning, followed by multi-letter extensions sorted in alphabetical
> order. The information is the same as the cpuinfo information, except
> that underscores are replaced by spaces and multi-letter extensions are
> simply sorted instead of following any ISA string ordering rule.
>
> The sample output below shows the difference between cpuinfo and lscpu.
>
> cpuinfo output:
> isa : rv64imafdch_zicbom_zicboz_zicntr_zicsr_zifencei_zihintntl_zihintpause_zihpm_zawrs_zfa_zba_zbb_zbc_zbs_smaia_ssaia_sstc
>
> lscpu output:
> ISA: rv64imafdch smaia ssaia sstc zawrs zba zbb zbc zbs zfa zicbom zicboz zicntr zicsr zifencei zihintntl zihintpause zihpm
>
> Signed-off-by: Sunil V L <sunilvl@ventanamicro.com>
> ---
> Changes in v2:
> 1) Format the ISA string instead of simply printing the same
> from cpuinfo. (Feedback from Andrew Jones).
> ---
> sys-utils/Makemodule.am | 1 +
> sys-utils/lscpu-cputype.c | 1 +
> sys-utils/lscpu-riscv.c | 57 +++++++++++++++++++++++++++++++++++++++
> sys-utils/lscpu.c | 5 ++++
> sys-utils/lscpu.h | 2 ++
> sys-utils/meson.build | 1 +
> 6 files changed, 67 insertions(+)
> create mode 100644 sys-utils/lscpu-riscv.c
>
Reviewed-by: Andrew Jones <ajones@ventanamicro.com>
next prev parent reply other threads:[~2025-03-11 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 16:06 [PATCH v2] lscpu: RISC-V: Print ISA information in summary Sunil V L
2025-03-11 16:19 ` Andrew Jones [this message]
2025-03-17 10:07 ` Karel Zak
2025-03-17 13:22 ` Karel Zak
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=20250311-8617d8509ac9d1ed6a3dbc82@orel \
--to=ajones@ventanamicro.com \
--cc=alexghiti@rivosinc.com \
--cc=apatel@ventanamicro.com \
--cc=atishp@rivosinc.com \
--cc=bjorn@kernel.org \
--cc=conor@kernel.org \
--cc=kzak@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=samuel.holland@sifive.com \
--cc=sunilvl@ventanamicro.com \
--cc=util-linux@vger.kernel.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