From: Conor Dooley <conor.dooley@microchip.com>
To: Andrew Jones <ajones@ventanamicro.com>
Cc: <linux-riscv@lists.infradead.org>, <paul.walmsley@sifive.com>,
<palmer@dabbelt.com>, <aou@eecs.berkeley.edu>,
<evan@rivosinc.com>, <apatel@ventanamicro.com>
Subject: Re: [PATCH 3/6] RISC-V: hwprobe: Expose Zicboz extension and its block size
Date: Thu, 10 Aug 2023 12:33:54 +0100 [thread overview]
Message-ID: <20230810-rifling-spelling-84cb162991ab@wendy> (raw)
In-Reply-To: <20230810-0c9993116a87372bf4fcfe9e@orel>
[-- Attachment #1.1: Type: text/plain, Size: 886 bytes --]
On Thu, Aug 10, 2023 at 12:57:30PM +0200, Andrew Jones wrote:
> On Thu, Aug 10, 2023 at 10:49:59AM +0100, Conor Dooley wrote:
> > On Wed, Aug 09, 2023 at 01:55:20PM +0200, Andrew Jones wrote:
> > > +#define EXT_KEY(ext) \
> > > + do { \
> > > + if (__riscv_isa_extension_available(isainfo->isa, RISCV_ISA_EXT_##ext)) \
> > > + pair->value |= RISCV_HWPROBE_EXT_##ext; \
> > > + else \
> > > + missing |= RISCV_HWPROBE_EXT_##ext; \
> > > + } while (false)
> >
> > Would you mind adding a comment here that using this macro is only
> > permitted for extensions that can be used by userspace regardless of kernel
> > config options?
>
> I can do that. Then, as part of the "extension available" API rework, we
> can maybe drop the comment when we use the new call, which will be
> documented to say that as well.
Yeah, exactly.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-08-10 11:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 11:55 [PATCH 0/6] RISC-V: Enable cbo.zero in usermode Andrew Jones
2023-08-09 11:55 ` [PATCH 1/6] RISC-V: Make zicbom/zicboz errors consistent Andrew Jones
2023-08-10 9:35 ` Conor Dooley
2023-08-09 11:55 ` [PATCH 2/6] RISC-V: Enable cbo.zero in usermode Andrew Jones
2023-08-09 16:00 ` Evan Green
2023-08-09 16:58 ` Andrew Jones
2023-08-09 18:12 ` Conor Dooley
2023-08-10 7:31 ` Andrew Jones
2023-08-10 9:34 ` Conor Dooley
2023-08-10 10:54 ` Andrew Jones
2023-08-10 13:23 ` Conor Dooley
2023-08-09 19:40 ` Evan Green
2023-08-09 11:55 ` [PATCH 3/6] RISC-V: hwprobe: Expose Zicboz extension and its block size Andrew Jones
2023-08-09 16:00 ` Evan Green
2023-08-10 9:49 ` Conor Dooley
2023-08-10 10:57 ` Andrew Jones
2023-08-10 11:33 ` Conor Dooley [this message]
2023-08-09 11:55 ` [PATCH 4/6] RISC-V: selftests: Statically link hwprobe test Andrew Jones
2023-08-10 9:36 ` Conor Dooley
2023-08-09 11:55 ` [PATCH 5/6] RISC-V: selftests: Convert hwprobe test to kselftest API Andrew Jones
2023-08-09 11:55 ` [PATCH 6/6] RISC-V: selftests: Add CBO tests Andrew Jones
2023-08-30 13:20 ` [PATCH 0/6] RISC-V: Enable cbo.zero in usermode patchwork-bot+linux-riscv
2023-08-30 16:22 ` Andrew Jones
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=20230810-rifling-spelling-84cb162991ab@wendy \
--to=conor.dooley@microchip.com \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=evan@rivosinc.com \
--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