From: Florian Weimer <fweimer@redhat.com>
To: Peter Bergner <bergner@oss.tenstorrent.com>
Cc: "Andy Chiu" <tchiu@tenstorrent.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Paul Walmsley" <pjw@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>,
linux-doc@vger.kernel.org, linux-riscv@lists.infradead.org,
kito.cheng@sifive.com, dfustini@oss.tenstorrent.com,
greentime.hu@sifive.com,
"Andrew Jones" <andrew.jones@oss.qualcomm.com>,
"Nutty Liu" <nutty.liu@hotmail.com>,
"Pincheng Wang" <pincheng.plct@isrc.iscas.ac.cn>,
"Yao Zihong" <zihong.plct@isrc.iscas.ac.cn>,
"Xu Lu" <luxu.kernel@bytedance.com>,
"Aleksa Paunovic" <aleksa.paunovic@htecgroup.com>,
"Jingwei Wang" <wangjingwei@iscas.ac.cn>,
"Zong Li" <zong.li@sifive.com>,
"Deepak Gupta" <debug@rivosinc.com>,
"Clément Léger" <cleger@rivosinc.com>,
linux-api@vger.kernel.org,
"Jeffrey Law" <jeffrey.law@oss.qualcomm.com>
Subject: Re: [EXT] Re: [PATCH 1/2] riscv: hwprobe: export the availability of vector to user
Date: Thu, 06 Aug 2026 08:31:48 +0200 [thread overview]
Message-ID: <lhuik5n4v57.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <cc671848-f954-41bf-b7a9-ba34c29593ec@oss.tenstorrent.com> (Peter Bergner's message of "Wed, 5 Aug 2026 13:40:27 -0500")
* Peter Bergner:
>> We only get a true userspace simplification over hwprobe + prctl if we
>> can disable vector extension usage if the kernel does not support
>> RISCV_HWPROBE_KEY_EXT_ENABLED (so a V usage regression for older
>> kernels). Otherwise we'd have to use the new approach and, as a
>> fallback, the old combination of hwprobe and prctl.
>
> Since the kernel ignores unknown keys, we do get a userspace simplification
> over hwprobe + prctl. The plan is for our GLIBC IFUNC resolvers to just have
> one hwprobe call (as they do now) with RISCV_HWPROBE_KEY_EXT_ENABLED as the
> first key and RISCV_HWPROBE_KEY_IMA_EXT_0 as the second key.
And if RISCV_HWPROBE_KEY_IMA_EXT_0 comes back at -1, we'd turn on V
unconditionally? That still leaves the existing bug on old kernels, but
at least the bug goes away with a kernel upgrade. This isn't too bad.
Thanks,
Florian
next prev parent reply other threads:[~2026-08-06 6:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260723222109.2229089-1-tchiu@tenstorrent.com>
2026-07-23 22:20 ` [PATCH 1/2] riscv: hwprobe: export the availability of vector to user Andy Chiu
2026-07-24 12:53 ` Florian Weimer
2026-08-05 18:40 ` [EXT] " Peter Bergner
2026-08-06 6:31 ` Florian Weimer [this message]
2026-08-06 17:09 ` Peter Bergner
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=lhuik5n4v57.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=aleksa.paunovic@htecgroup.com \
--cc=alex@ghiti.fr \
--cc=andrew.jones@oss.qualcomm.com \
--cc=aou@eecs.berkeley.edu \
--cc=bergner@oss.tenstorrent.com \
--cc=cleger@rivosinc.com \
--cc=corbet@lwn.net \
--cc=debug@rivosinc.com \
--cc=dfustini@oss.tenstorrent.com \
--cc=greentime.hu@sifive.com \
--cc=jeffrey.law@oss.qualcomm.com \
--cc=kito.cheng@sifive.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=luxu.kernel@bytedance.com \
--cc=nutty.liu@hotmail.com \
--cc=palmer@dabbelt.com \
--cc=pincheng.plct@isrc.iscas.ac.cn \
--cc=pjw@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tchiu@tenstorrent.com \
--cc=wangjingwei@iscas.ac.cn \
--cc=zihong.plct@isrc.iscas.ac.cn \
--cc=zong.li@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