From: patchwork-bot+linux-riscv@kernel.org
To: Evan Green <evan@rivosinc.com>
Cc: linux-riscv@lists.infradead.org, palmer@rivosinc.com,
apatel@ventanamicro.com, aou@eecs.berkeley.edu, corbet@lwn.net,
abrestic@rivosinc.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, conor.dooley@microchip.com,
coelacanthus@outlook.com, jszhang@kernel.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
heiko.stuebner@vrull.eu, ajones@ventanamicro.com
Subject: Re: [PATCH v2 0/3] RISC-V: Export Zba, Zbb to usermode via hwprobe
Date: Tue, 20 Jun 2023 01:00:23 +0000 [thread overview]
Message-ID: <168722282387.22807.6974446089239901729.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230509182504.2997252-1-evan@rivosinc.com>
Hello:
This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Tue, 9 May 2023 11:25:00 -0700 you wrote:
> This change detects the presence of Zba, Zbb, and Zbs 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 and Zbs 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.
>
> [...]
Here is the summary with links:
- [v2,1/3] RISC-V: Add Zba, Zbs extension probing
https://git.kernel.org/riscv/c/c6699baf1064
- [v2,2/3] RISC-V: Track ISA extensions per hart
https://git.kernel.org/riscv/c/82e9c66e81c8
- [v2,3/3] RISC-V: hwprobe: Expose Zba, Zbb, and Zbs
https://git.kernel.org/riscv/c/c0baf321038d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-06-20 1:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 18:25 [PATCH v2 0/3] RISC-V: Export Zba, Zbb to usermode via hwprobe Evan Green
2023-05-09 18:25 ` [PATCH v2 1/3] RISC-V: Add Zba, Zbs extension probing Evan Green
2023-05-09 18:29 ` Conor Dooley
2023-05-09 18:34 ` Evan Green
2023-05-10 14:45 ` Heiko Stübner
2023-06-19 23:44 ` Palmer Dabbelt
2023-05-09 18:25 ` [PATCH v2 2/3] RISC-V: Track ISA extensions per hart Evan Green
2023-05-09 18:25 ` [PATCH v2 3/3] RISC-V: hwprobe: Expose Zba, Zbb, and Zbs Evan Green
2023-05-09 18:33 ` Conor Dooley
2023-05-10 14:47 ` Heiko Stübner
2023-06-19 23:55 ` Palmer Dabbelt
2023-06-19 22:07 ` [PATCH v2 0/3] RISC-V: Export Zba, Zbb to usermode via hwprobe Palmer Dabbelt
2023-06-20 1:00 ` patchwork-bot+linux-riscv [this message]
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=168722282387.22807.6974446089239901729.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--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=evan@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