From: Andrew Jones <ajones@ventanamicro.com>
To: yunhui cui <cuiyunhui@bytedance.com>
Cc: Samuel Holland <samuel.holland@sifive.com>,
alexghiti@rivosinc.com, andybnac@gmail.com,
aou@eecs.berkeley.edu, charlie@rivosinc.com, cleger@rivosinc.com,
conor.dooley@microchip.com, conor@kernel.org, corbet@lwn.net,
evan@rivosinc.com, jesse@rivosinc.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
linux-riscv@lists.infradead.org, palmer@dabbelt.com,
paul.walmsley@sifive.com, shuah@kernel.org
Subject: Re: [External] Re: [PATCH v4 2/3] RISC-V: hwprobe: Expose Zicbom extension and its block size
Date: Tue, 14 Jan 2025 13:42:51 +0100 [thread overview]
Message-ID: <20250114-6f373c6dd685cf322c89e7d5@orel> (raw)
In-Reply-To: <CAEEQ3wm7-O5U3jjbQ1+XgVvk+G7csMPAxzGoV=K5WczCOsbQ5g@mail.gmail.com>
On Tue, Jan 14, 2025 at 08:17:02PM +0800, yunhui cui wrote:
> Hi Samuel,
>
> On Tue, Jan 14, 2025 at 1:28 PM Samuel Holland
> <samuel.holland@sifive.com> wrote:
> >
> > Hi Yunhui,
> >
> > On 2025-01-13 8:19 PM, Yunhui Cui wrote:
> > > Expose Zicbom through hwprobe and also provide a key to extract its
> > > respective block size.
> > >
> > > Signed-off-by: Yunhui Cui <cuiyunhui@bytedance.com>
> > > ---
> > > Documentation/arch/riscv/hwprobe.rst | 6 ++++++
> > > arch/riscv/include/asm/hwprobe.h | 2 +-
> > > arch/riscv/include/uapi/asm/hwprobe.h | 2 ++
> > > arch/riscv/kernel/sys_hwprobe.c | 6 ++++++
> > > 4 files changed, 15 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/Documentation/arch/riscv/hwprobe.rst b/Documentation/arch/riscv/hwprobe.rst
> > > index 955fbcd19ce9..0ea7754b2049 100644
> > > --- a/Documentation/arch/riscv/hwprobe.rst
> > > +++ b/Documentation/arch/riscv/hwprobe.rst
> > > @@ -242,6 +242,9 @@ The following keys are defined:
> > > * :c:macro:`RISCV_HWPROBE_EXT_SUPM`: The Supm extension is supported as
> > > defined in version 1.0 of the RISC-V Pointer Masking extensions.
> > >
> > > + * :c:macro:`RISCV_HWPROBE_EXT_ZICBOM`: The Zicbom extension is supported, as
> > > + ratified in commit 3dd606f ("Create cmobase-v1.0.pdf") of riscv-CMOs.
> > > +
> > > * :c:macro:`RISCV_HWPROBE_KEY_CPUPERF_0`: Deprecated. Returns similar values to
> > > :c:macro:`RISCV_HWPROBE_KEY_MISALIGNED_SCALAR_PERF`, but the key was
> > > mistakenly classified as a bitmask rather than a value.
> > > @@ -281,6 +284,9 @@ The following keys are defined:
> > > * :c:macro:`RISCV_HWPROBE_KEY_MISALIGNED_VECTOR_PERF`: An enum value describing the
> > > performance of misaligned vector accesses on the selected set of processors.
> > >
> > > +* :c:macro:`RISCV_HWPROBE_KEY_ZICBOM_BLOCK_SIZE`: An unsigned int which
> > > + represents the size of the Zicbom block in bytes.
> > > +
> > > * :c:macro:`RISCV_HWPROBE_MISALIGNED_VECTOR_UNKNOWN`: The performance of misaligned
> > > vector accesses is unknown.
> >
> > The new key needs to go further down, below this list of possible values for the
> > previous key.
> I guess you mean to put it after
> RISCV_HWPROBE_MISALIGNED_VECTOR_UNSUPPORTED, right?
Yes, notice how all the RISCV_HWPROBE_MISALIGNED_VECTOR_* defines are
indented under RISCV_HWPROBE_KEY_MISALIGNED_VECTOR_PERF indicating
they're part of the RISCV_HWPROBE_KEY_MISALIGNED_VECTOR_PERF group.
Thanks,
drew
>
> >
> > Regards,
> > Samuel
> >
> > >
> > > diff --git a/arch/riscv/include/asm/hwprobe.h b/arch/riscv/include/asm/hwprobe.h
> > > index 1ce1df6d0ff3..89379f9a2e6e 100644
> > > --- a/arch/riscv/include/asm/hwprobe.h
> > > +++ b/arch/riscv/include/asm/hwprobe.h
> > > @@ -8,7 +8,7 @@
> > >
> > > #include <uapi/asm/hwprobe.h>
> > >
> > > -#define RISCV_HWPROBE_MAX_KEY 10
> > > +#define RISCV_HWPROBE_MAX_KEY 11
> > >
> > > static inline bool riscv_hwprobe_key_is_valid(__s64 key)
> > > {
> > > diff --git a/arch/riscv/include/uapi/asm/hwprobe.h b/arch/riscv/include/uapi/asm/hwprobe.h
> > > index 3af142b99f77..b15c0bd83ef2 100644
> > > --- a/arch/riscv/include/uapi/asm/hwprobe.h
> > > +++ b/arch/riscv/include/uapi/asm/hwprobe.h
> > > @@ -73,6 +73,7 @@ struct riscv_hwprobe {
> > > #define RISCV_HWPROBE_EXT_ZCMOP (1ULL << 47)
> > > #define RISCV_HWPROBE_EXT_ZAWRS (1ULL << 48)
> > > #define RISCV_HWPROBE_EXT_SUPM (1ULL << 49)
> > > +#define RISCV_HWPROBE_EXT_ZICBOM (1ULL << 50)
> > > #define RISCV_HWPROBE_KEY_CPUPERF_0 5
> > > #define RISCV_HWPROBE_MISALIGNED_UNKNOWN (0 << 0)
> > > #define RISCV_HWPROBE_MISALIGNED_EMULATED (1 << 0)
> > > @@ -94,6 +95,7 @@ struct riscv_hwprobe {
> > > #define RISCV_HWPROBE_MISALIGNED_VECTOR_SLOW 2
> > > #define RISCV_HWPROBE_MISALIGNED_VECTOR_FAST 3
> > > #define RISCV_HWPROBE_MISALIGNED_VECTOR_UNSUPPORTED 4
> > > +#define RISCV_HWPROBE_KEY_ZICBOM_BLOCK_SIZE 11
> > > /* Increase RISCV_HWPROBE_MAX_KEY when adding items. */
> > >
> > > /* Flags */
> > > diff --git a/arch/riscv/kernel/sys_hwprobe.c b/arch/riscv/kernel/sys_hwprobe.c
> > > index cb93adfffc48..04150e62f998 100644
> > > --- a/arch/riscv/kernel/sys_hwprobe.c
> > > +++ b/arch/riscv/kernel/sys_hwprobe.c
> > > @@ -106,6 +106,7 @@ static void hwprobe_isa_ext0(struct riscv_hwprobe *pair,
> > > EXT_KEY(ZCA);
> > > EXT_KEY(ZCB);
> > > EXT_KEY(ZCMOP);
> > > + EXT_KEY(ZICBOM);
> > > EXT_KEY(ZICBOZ);
> > > EXT_KEY(ZICOND);
> > > EXT_KEY(ZIHINTNTL);
> > > @@ -278,6 +279,11 @@ static void hwprobe_one_pair(struct riscv_hwprobe *pair,
> > > if (hwprobe_ext0_has(cpus, RISCV_HWPROBE_EXT_ZICBOZ))
> > > pair->value = riscv_cboz_block_size;
> > > break;
> > > + case RISCV_HWPROBE_KEY_ZICBOM_BLOCK_SIZE:
> > > + pair->value = 0;
> > > + if (hwprobe_ext0_has(cpus, RISCV_HWPROBE_EXT_ZICBOM))
> > > + pair->value = riscv_cbom_block_size;
> > > + break;
> > > case RISCV_HWPROBE_KEY_HIGHEST_VIRT_ADDRESS:
> > > pair->value = user_max_virt_addr();
> > > break;
> >
>
> Thanks,
> Yunhui
next prev parent reply other threads:[~2025-01-14 12:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 2:19 [PATCH v4 0/3] Enable Zicbom in usermode Yunhui Cui
2025-01-14 2:19 ` [PATCH v4 1/3] RISC-V: Enable cbo.clean/flush " Yunhui Cui
2025-01-14 2:19 ` [PATCH v4 2/3] RISC-V: hwprobe: Expose Zicbom extension and its block size Yunhui Cui
2025-01-14 5:28 ` Samuel Holland
2025-01-14 12:17 ` [External] " yunhui cui
2025-01-14 12:42 ` Andrew Jones [this message]
2025-01-14 2:19 ` [PATCH v4 3/3] RISC-V: selftests: Add TEST_ZICBOM into CBO tests Yunhui Cui
2025-01-14 5:32 ` Samuel Holland
2025-01-14 8:18 ` 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=20250114-6f373c6dd685cf322c89e7d5@orel \
--to=ajones@ventanamicro.com \
--cc=alexghiti@rivosinc.com \
--cc=andybnac@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=charlie@rivosinc.com \
--cc=cleger@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=corbet@lwn.net \
--cc=cuiyunhui@bytedance.com \
--cc=evan@rivosinc.com \
--cc=jesse@rivosinc.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=samuel.holland@sifive.com \
--cc=shuah@kernel.org \
/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