From: Guodong Xu <guodong.xu@oss.qualcomm.com>
To: Charlie Jenkins <thecharlesjenkins@gmail.com>
Cc: "Radim Krčmář" <radim.krcmar@oss.qualcomm.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
"Paul Walmsley" <pjw@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Alexandre Ghiti" <alex@ghiti.fr>,
"Samuel Holland" <samuel.holland@sifive.com>,
"Andy Chiu" <andybnac@gmail.com>, "Zong Li" <zong.li@sifive.com>
Subject: Re: [PATCH 5/6] riscv: hwprobe: Report XTheadVector only when available
Date: Sun, 08 Nov 2026 09:00:46 -0500 [thread overview]
Message-ID: <c1a723190b71b663d73be7cb9f5141d5.guodong.xu@oss.qualcomm.com> (raw)
In-Reply-To: <asX9uMyiJMAzjIFF@blinky>
Hi Charlie, Radim,
On Wed, 7 Oct 2026 01:07:20 -0700, Charlie Jenkins wrote:
> On Wed, Oct 07, 2026 at 09:59:30AM +0200, Radim Krčmář wrote:
> > 2026-10-06T16:54:53-07:00, Charlie Jenkins <thecharlesjenkins@gmail.com>:
> [...]
> > > Is
> > > it worthwhile to make this change?
> >
> > I think that it's sensible to mimic the validation we do for the
> > non-vendor extension, but users of vendor extensions likely already have
> > to go out of their way to utilize them, so they can do the sanity checks
> > too... I can drop the last two patches in v2.
>
> I don't know, it seems better to keep standardization if possible and
> leave the check in here to mimic the standard extensions?
+1 to keeping patches 5 and 6 in v2.
Having the vendor keys follow the same rule as the standard ones keeps
the meaning of every hwprobe bit uniform, which I think is a must.
Guodong
next prev parent reply other threads:[~2026-11-08 14:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 7:52 [PATCH 0/6] riscv: hwprobe: do not report disabled extensions Radim Krčmář
2026-10-06 7:52 ` [PATCH 1/6] riscv: hwprobe: Report FP extensions only when available Radim Krčmář
2026-10-06 23:54 ` Charlie Jenkins
2026-10-07 7:46 ` Radim Krčmář
2026-10-07 8:05 ` Charlie Jenkins
2026-11-08 4:16 ` guodong.xu
2026-11-09 13:40 ` Radim Krčmář
2026-10-16 21:04 ` Andy Chiu
2026-10-06 7:52 ` [PATCH 2/6] riscv: hwprobe: Report Zicbom and Zicboz " Radim Krčmář
2026-10-16 4:28 ` Charlie Jenkins
2026-10-16 21:06 ` Andy Chiu
2026-11-08 10:45 ` Guodong Xu
2026-10-06 7:53 ` [PATCH 3/6] riscv: hwprobe: Report Zicfilp and Zicfiss " Radim Krčmář
2026-10-16 4:28 ` Charlie Jenkins
2026-10-16 21:09 ` Andy Chiu
2026-11-08 10:05 ` Guodong Xu
2026-10-06 7:53 ` [PATCH 4/6] riscv: hwprobe: Report Supm " Radim Krčmář
2026-10-16 4:28 ` Charlie Jenkins
2026-10-16 21:26 ` Andy Chiu
2026-10-16 21:45 ` Andy Chiu
2026-10-20 10:00 ` Radim Krčmář
2026-11-08 11:24 ` [PATCH 4/6] " Guodong Xu
2026-11-09 13:41 ` Radim Krčmář
2026-10-06 7:53 ` [PATCH 5/6] riscv: hwprobe: Report XTheadVector " Radim Krčmář
2026-10-06 23:54 ` Charlie Jenkins
2026-10-07 7:59 ` Radim Krčmář
2026-10-07 8:07 ` Charlie Jenkins
2026-11-08 14:00 ` Guodong Xu [this message]
2026-10-16 21:48 ` Andy Chiu
2026-10-06 7:53 ` [PATCH 6/6] riscv: hwprobe: Report SiFive vector extensions " Radim Krčmář
2026-10-16 21:55 ` Andy Chiu
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=c1a723190b71b663d73be7cb9f5141d5.guodong.xu@oss.qualcomm.com \
--to=guodong.xu@oss.qualcomm.com \
--cc=alex@ghiti.fr \
--cc=andybnac@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=radim.krcmar@oss.qualcomm.com \
--cc=samuel.holland@sifive.com \
--cc=thecharlesjenkins@gmail.com \
--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
all inboxes | Powered by JetHome®