From: Conor Dooley <conor@kernel.org>
To: Evan Green <evan@rivosinc.com>
Cc: "Palmer Dabbelt" <palmer@dabbelt.com>,
"Yangyu Chen" <cyy@cyyself.name>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alexghiti@rivosinc.com>,
"Andrew Jones" <ajones@ventanamicro.com>,
"Andy Chiu" <andy.chiu@sifive.com>,
"Ben Dooks" <ben.dooks@codethink.co.uk>,
"Björn Töpel" <bjorn@rivosinc.com>,
"Charlie Jenkins" <charlie@rivosinc.com>,
"Clément Léger" <cleger@rivosinc.com>,
"Conor Dooley" <conor.dooley@microchip.com>,
"Costa Shulyupin" <costa.shul@redhat.com>,
"Erick Archer" <erick.archer@gmx.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v2 2/2] RISC-V: hwprobe: Add SCALAR to misaligned perf defines
Date: Wed, 26 Jun 2024 15:34:07 +0100 [thread overview]
Message-ID: <20240626-ungraded-legend-65480eabd255@spud> (raw)
In-Reply-To: <CALs-HsuEc9ympGsQP3bvXaowiAj0bq3nvD=9CcX0NNMza+79OA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5346 bytes --]
On Tue, Jun 25, 2024 at 12:08:09PM -0700, Evan Green wrote:
> On Tue, Jun 25, 2024 at 11:35 AM Conor Dooley <conor@kernel.org> wrote:
> >
> > On Tue, Jun 25, 2024 at 09:51:21AM -0700, Evan Green wrote:
> > > In preparation for misaligned vector performance hwprobe keys, rename
> > > the hwprobe key values associated with misaligned scalar accesses to
> > > include the term SCALAR.
> > >
> > > Signed-off-by: Evan Green <evan@rivosinc.com>
> > >
> > > ---
> > >
> > > Changes in v2:
> > > - Added patch to rename misaligned perf key values (Palmer)
> > >
> > > Documentation/arch/riscv/hwprobe.rst | 20 ++++++++++----------
> > > arch/riscv/include/uapi/asm/hwprobe.h | 10 +++++-----
> > > arch/riscv/kernel/sys_hwprobe.c | 10 +++++-----
> > > arch/riscv/kernel/traps_misaligned.c | 6 +++---
> > > arch/riscv/kernel/unaligned_access_speed.c | 12 ++++++------
> > > 5 files changed, 29 insertions(+), 29 deletions(-)
> > >
> > > diff --git a/Documentation/arch/riscv/hwprobe.rst b/Documentation/arch/riscv/hwprobe.rst
> > > index c9f570b1ab60..83f7f3c1347f 100644
> > > --- a/Documentation/arch/riscv/hwprobe.rst
> > > +++ b/Documentation/arch/riscv/hwprobe.rst
> > > @@ -215,22 +215,22 @@ The following keys are defined:
> > > the performance of misaligned scalar word accesses on the selected set of
> > > processors.
> > >
> > > - * :c:macro:`RISCV_HWPROBE_MISALIGNED_UNKNOWN`: The performance of misaligned
> > > - accesses is unknown.
> > > + * :c:macro:`RISCV_HWPROBE_MISALIGNED_SCALAR_UNKNOWN`: The performance of
> > > + misaligned accesses is unknown.
> > >
> > > - * :c:macro:`RISCV_HWPROBE_MISALIGNED_EMULATED`: Misaligned accesses are
> > > + * :c:macro:`RISCV_HWPROBE_MISALIGNED_SCALAR_EMULATED`: Misaligned accesses are
> > > emulated via software, either in or below the kernel. These accesses are
> > > always extremely slow.
> > >
> > > - * :c:macro:`RISCV_HWPROBE_MISALIGNED_SLOW`: Misaligned word accesses are
> > > - slower than equivalent byte accesses. Misaligned accesses may be supported
> > > - directly in hardware, or trapped and emulated by software.
> > > + * :c:macro:`RISCV_HWPROBE_MISALIGNED_SCALAR_SLOW`: Misaligned word accesses
> > > + are slower than equivalent byte accesses. Misaligned accesses may be
> > > + supported directly in hardware, or trapped and emulated by software.
> > >
> > > - * :c:macro:`RISCV_HWPROBE_MISALIGNED_FAST`: Misaligned word accesses are
> > > - faster than equivalent byte accesses.
> > > + * :c:macro:`RISCV_HWPROBE_MISALIGNED_SCALAR_FAST`: Misaligned word accesses
> > > + are faster than equivalent byte accesses.
> > >
> > > - * :c:macro:`RISCV_HWPROBE_MISALIGNED_UNSUPPORTED`: Misaligned accesses are
> > > - not supported at all and will generate a misaligned address fault.
> > > + * :c:macro:`RISCV_HWPROBE_MISALIGNED_SCALAR_UNSUPPORTED`: Misaligned accesses
> > > + are not supported at all and will generate a misaligned address fault.
> > >
> > > * :c:macro:`RISCV_HWPROBE_KEY_ZICBOZ_BLOCK_SIZE`: An unsigned int which
> > > represents the size of the Zicboz block in bytes.
> > > diff --git a/arch/riscv/include/uapi/asm/hwprobe.h b/arch/riscv/include/uapi/asm/hwprobe.h
> > > index 22073533cea8..e11684d8ae1c 100644
> > > --- a/arch/riscv/include/uapi/asm/hwprobe.h
> > > +++ b/arch/riscv/include/uapi/asm/hwprobe.h
> > > @@ -66,11 +66,11 @@ struct riscv_hwprobe {
> > > #define RISCV_HWPROBE_EXT_ZVE64F (1ULL << 40)
> > > #define RISCV_HWPROBE_EXT_ZVE64D (1ULL << 41)
> > > #define RISCV_HWPROBE_KEY_CPUPERF_0 5
> > > -#define RISCV_HWPROBE_MISALIGNED_UNKNOWN 0
> > > -#define RISCV_HWPROBE_MISALIGNED_EMULATED 1
> > > -#define RISCV_HWPROBE_MISALIGNED_SLOW 2
> > > -#define RISCV_HWPROBE_MISALIGNED_FAST 3
> > > -#define RISCV_HWPROBE_MISALIGNED_UNSUPPORTED 4
> > > +#define RISCV_HWPROBE_MISALIGNED_SCALAR_UNKNOWN 0
> > > +#define RISCV_HWPROBE_MISALIGNED_SCALAR_EMULATED 1
> > > +#define RISCV_HWPROBE_MISALIGNED_SCALAR_SLOW 2
> > > +#define RISCV_HWPROBE_MISALIGNED_SCALAR_FAST 3
> > > +#define RISCV_HWPROBE_MISALIGNED_SCALAR_UNSUPPORTED 4
> > > #define RISCV_HWPROBE_MISALIGNED_MASK 7
> >
> > How come the "old" names do not need to be preserved for userspace?
>
> It depends on what exactly the big userspace compatibility rule is.
> This preserves binary compatibility, which I think is the big one, but
> breaks source compatibility, though with an easy translation to fix.
> We could keep the old names around, but then it seems sort of silly to
> introduce the new names. I introduced this patch upon request, so I
> don't personally have a horse in the race on this one.
So apparently this isn't quite Palmer actually wanted. In today's call
he suggested that he'd send a new version himself, but also that what we
should do define a new key for scalar /and/ new add new defines values that
contain the word scalar, retaining the old defines. The values can of
course be the same.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-06-26 14:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 16:51 [PATCH v2 0/2] RISC-V: hwprobe: Misaligned scalar perf fix and rename Evan Green
2024-06-25 16:51 ` [PATCH v2 1/2] RISC-V: hwprobe: Add MISALIGNED_PERF key Evan Green
2024-06-26 14:36 ` Conor Dooley
2024-06-26 15:55 ` Evan Green
2024-06-25 16:51 ` [PATCH v2 2/2] RISC-V: hwprobe: Add SCALAR to misaligned perf defines Evan Green
2024-06-25 18:33 ` Charlie Jenkins
2024-06-25 18:35 ` Conor Dooley
2024-06-25 19:08 ` Evan Green
2024-06-26 14:34 ` Conor Dooley [this message]
2024-06-26 15:44 ` Evan Green
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=20240626-ungraded-legend-65480eabd255@spud \
--to=conor@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=alexghiti@rivosinc.com \
--cc=andy.chiu@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=ben.dooks@codethink.co.uk \
--cc=bjorn@rivosinc.com \
--cc=charlie@rivosinc.com \
--cc=cleger@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=corbet@lwn.net \
--cc=costa.shul@redhat.com \
--cc=cyy@cyyself.name \
--cc=erick.archer@gmx.com \
--cc=evan@rivosinc.com \
--cc=gustavoars@kernel.org \
--cc=linux-doc@vger.kernel.org \
--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