public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Paul Walmsley <pjw@kernel.org>
To: Charlie Jenkins <charlie@rivosinc.com>
Cc: "Paul Walmsley" <pjw@kernel.org>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Alexandre Ghiti" <alex@ghiti.fr>,
	"Anup Patel" <anup@brainfault.org>,
	"Atish Patra" <atish.patra@linux.dev>,
	"Samuel Holland" <samuel.holland@sifive.com>,
	"Björn Töpel" <bjorn@kernel.org>,
	"Luke Nelson" <luke.r.nels@gmail.com>,
	"Xi Wang" <xi.wang@gmail.com>,
	"Eric Biggers" <ebiggers@kernel.org>,
	"Conor Dooley" <conor@kernel.org>,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	"Charlie Jenkins" <thecharlesjenkins@gmail.com>
Subject: Re: [PATCH RFC 00/10] riscv: Add support for rva23
Date: Wed, 14 Jan 2026 11:16:50 -0700 (MST)	[thread overview]
Message-ID: <9325a1ab-62e7-e61f-ab55-cc06b582a23a@kernel.org> (raw)
In-Reply-To: <20251210-profiles-v1-0-315a6ff2ca5a@gmail.com>

Hi Charlie,

On Wed, 10 Dec 2025, Charlie Jenkins wrote:

> I will be talking about rva23 at Plumbers this year and have this series
> as a draft of my ideas.
> 
> rva23 is a RVI profile to group together extensions that are expected to
> be found on high-performance systems.
> 
> This series:
> 1. Introduces a framework to add extensions to the kernel cflags
> 2. Adds a rva23 config option 
> 3. Optimizes riscv_has_extension_*
> 
> This is based on 6.18 plus
> https://lore.kernel.org/linux-riscv/20251020-riscv-altn-helper-wip-v4-0-ef941c87669a@iscas.ac.cn/.
> 
> Signed-off-by: Charlie Jenkins <thecharlesjenkins@gmail.com>

Thanks for sending these.  A few suggestions, for when you resend these 
patches:

- Please split the cleanup patches into a separate, predecessor series 
  from the patches that are designed to change the way that extensions are 
  handled.  The latter patches will probably take longer to reach 
  consensus around.

- Probably best not to characterize the latter set of patches as "RVA23 
  support" patches, since they won't affect the kernel's ability to 
  support RVA23.  These just enable building an RVA23-specific kernel.  
  It's not entirely clear to me that this is a win -- I assume the 
  argument would be that the performance benefit for some systems would 
  justify the additional complexity and the performance reduction for 
  other systems? -- but that's what we'd need to discuss.

- Continuing that line of thinking, I think we'd want to see some 
  performance measurements after these patches are applied, on 
  hardware, for both RVA23-specific kernels and non-RVA23-specific 
  kernels, and the latter on both non-RVA23 hardware and RVA23 hardware.


thanks,

- Paul

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

      parent reply	other threads:[~2026-01-14 18:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-10 16:13 [PATCH RFC 00/10] riscv: Add support for rva23 Charlie Jenkins
2025-12-10 16:13 ` [PATCH RFC 01/10] riscv: Standardize extension capitilization Charlie Jenkins
2026-01-15  2:48   ` Paul Walmsley
2026-01-15 16:03   ` Andrew Jones
2025-12-10 16:13 ` [PATCH RFC 02/10] riscv: kconfig: Reorganize extensions Charlie Jenkins
2025-12-10 16:13 ` [PATCH RFC 03/10] riscv: kconfig: Simply arch selection Charlie Jenkins
2025-12-10 16:13 ` [PATCH RFC 04/10] riscv: kconfig: Make extensions tristate Charlie Jenkins
2025-12-10 16:13 ` [PATCH RFC 05/10] riscv: kconfig: Add zve32x Charlie Jenkins
2025-12-10 16:13 ` [PATCH RFC 06/10] riscv: Makefile: Add enabled extensions to compiler flags Charlie Jenkins
2025-12-10 16:13 ` [PATCH RFC 07/10] riscv: kconfig: Make vendor extensions tristate Charlie Jenkins
2025-12-10 16:13 ` [PATCH RFC 08/10] riscv: Optimize cpufeature macros for extension assumptions Charlie Jenkins
2025-12-10 16:13 ` [PATCH RFC 09/10] riscv: kconfig: Add rva23 config Charlie Jenkins
2025-12-10 16:13 ` [PATCH RFC 10/10] riscv: csum: Remove inline assembly Charlie Jenkins
2026-01-14 18:16 ` Paul Walmsley [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=9325a1ab-62e7-e61f-ab55-cc06b582a23a@kernel.org \
    --to=pjw@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=anup@brainfault.org \
    --cc=atish.patra@linux.dev \
    --cc=bjorn@kernel.org \
    --cc=charlie@rivosinc.com \
    --cc=conor@kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=luke.r.nels@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=samuel.holland@sifive.com \
    --cc=thecharlesjenkins@gmail.com \
    --cc=xi.wang@gmail.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