From: Evan Green <evan@rivosinc.com>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: Anup Patel <apatel@ventanamicro.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Jonathan Corbet <corbet@lwn.net>,
Andrew Bresticker <abrestic@rivosinc.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>,
Evan Green <evan@rivosinc.com>,
Celeste Liu <coelacanthus@outlook.com>,
Jisheng Zhang <jszhang@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>, Dao Lu <daolu@rivosinc.com>,
Heiko Stuebner <heiko.stuebner@vrull.eu>,
linux-riscv@lists.infradead.org,
Andrew Jones <ajones@ventanamicro.com>
Subject: [PATCH 0/3] RISC-V: Export Zba, Zbb to usermode via hwprobe
Date: Fri, 28 Apr 2023 12:06:05 -0700 [thread overview]
Message-ID: <20230428190609.3239486-1-evan@rivosinc.com> (raw)
This change detects the presence of Zba and Zbb extensions and exports
them per-hart to userspace via the hwprobe mechanism. Glibc can then use
these in setting up hwcaps-based library search paths.
There's a little bit of extra housekeeping here: the first change adds
Zba to the set of extensions the kernel recognizes, and the second
change starts tracking ISA features per-hart (in addition to the ANDed
mask of features across all harts which the kernel uses to make
decisions). Now that we track the ISA information per-hart, we could
even fix up /proc/cpuinfo to accurately report extension per-hart,
though I've left that out of this series for now.
Evan Green (3):
RISC-V: Add Zba extension probing
RISC-V: Track ISA extensions per hart
RISC-V: hwprobe: Expose Zba and Zbb
Documentation/riscv/hwprobe.rst | 7 +++++
arch/riscv/include/asm/cpufeature.h | 10 +++++++
arch/riscv/include/asm/hwcap.h | 1 +
arch/riscv/include/uapi/asm/hwprobe.h | 2 ++
arch/riscv/kernel/cpu.c | 1 +
arch/riscv/kernel/cpufeature.c | 19 ++++++++----
arch/riscv/kernel/sys_riscv.c | 43 ++++++++++++++++++++++-----
7 files changed, 70 insertions(+), 13 deletions(-)
--
2.25.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2023-04-28 19:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 19:06 Evan Green [this message]
2023-04-28 19:06 ` [PATCH 1/3] RISC-V: Add Zba extension probing Evan Green
2023-04-29 13:41 ` Conor Dooley
2023-04-29 20:07 ` Palmer Dabbelt
2023-04-28 19:06 ` [PATCH 2/3] RISC-V: Track ISA extensions per hart Evan Green
2023-04-29 13:36 ` Conor Dooley
2023-04-29 20:07 ` Palmer Dabbelt
2023-04-28 19:06 ` [PATCH 3/3] RISC-V: hwprobe: Expose Zba and Zbb Evan Green
2023-04-29 13:40 ` Conor Dooley
2023-04-29 20:07 ` Palmer Dabbelt
2023-05-01 15:33 ` Evan Green
2023-04-29 12:34 ` [PATCH 0/3] RISC-V: Export Zba, Zbb to usermode via hwprobe Andrew Jones
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=20230428190609.3239486-1-evan@rivosinc.com \
--to=evan@rivosinc.com \
--cc=abrestic@rivosinc.com \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=coelacanthus@outlook.com \
--cc=conor.dooley@microchip.com \
--cc=corbet@lwn.net \
--cc=daolu@rivosinc.com \
--cc=heiko.stuebner@vrull.eu \
--cc=jszhang@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.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