From: Conor Dooley <conor@kernel.org>
To: Charlie Jenkins <charlie@rivosinc.com>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Conor Dooley <conor.dooley@microchip.com>,
Evan Green <evan@rivosinc.com>, Andy Chiu <andy.chiu@sifive.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] riscv: Extend cpufeature.c to detect vendor extensions
Date: Thu, 13 Jun 2024 15:44:26 +0100 [thread overview]
Message-ID: <20240613-award-dubiously-49252229b020@spud> (raw)
In-Reply-To: <20240609-support_vendor_extensions-v2-1-9a43f1fdcbb9@rivosinc.com>
[-- Attachment #1: Type: text/plain, Size: 749 bytes --]
On Sun, Jun 09, 2024 at 09:34:14PM -0700, Charlie Jenkins wrote:
> Instead of grouping all vendor extensions into the same riscv_isa_ext
> that standard instructions use, create a struct
> "riscv_isa_vendor_ext_data_list" that allows each vendor to maintain
> their vendor extensions independently of the standard extensions.
> xandespmu is currently the only vendor extension so that is the only
> extension that is affected by this change.
>
> An additional benefit of this is that the extensions of each vendor can
> be conditionally enabled. A config RISCV_ISA_VENDOR_EXT_ANDES has been
> added to allow for that.
>
> Signed-off-by: Charlie Jenkins <charlie@rivosinc.com>
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-06-13 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 4:34 [PATCH v2 0/4] riscv: Separate vendor extensions from standard extensions Charlie Jenkins
2024-06-10 4:34 ` [PATCH v2 1/4] riscv: Extend cpufeature.c to detect vendor extensions Charlie Jenkins
2024-06-13 14:44 ` Conor Dooley [this message]
2024-06-21 7:37 ` Andy Chiu
2024-07-02 9:54 ` Yu-Chien Peter Lin
2024-06-10 4:34 ` [PATCH v2 2/4] riscv: Add vendor extensions to /proc/cpuinfo Charlie Jenkins
2024-06-10 4:34 ` [PATCH v2 3/4] riscv: Introduce vendor variants of extension helpers Charlie Jenkins
2024-06-21 8:37 ` Andy Chiu
2024-06-10 4:34 ` [PATCH v2 4/4] riscv: cpufeature: Extract common elements from extension checking Charlie Jenkins
2024-06-21 8:38 ` Andy Chiu
2024-06-13 14:45 ` [PATCH v2 0/4] riscv: Separate vendor extensions from standard extensions Conor Dooley
2024-06-13 17:37 ` Charlie Jenkins
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=20240613-award-dubiously-49252229b020@spud \
--to=conor@kernel.org \
--cc=andy.chiu@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=charlie@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=evan@rivosinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.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
all inboxes | Powered by JetHome®