From: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Sandiford <Richard.Sandiford@arm.com>
Subject: RE: [PATCH] libatomic: Improve ifunc selection on AArch64
Date: Fri, 10 Nov 2023 10:00:10 +0000 [thread overview]
Message-ID: <PAXPR08MB69260BD4D15052B0B852B93393AEA@PAXPR08MB6926.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <DB3PR08MB898680B163DABE308A1AABD883AAA@DB3PR08MB8986.eurprd08.prod.outlook.com>
Hi Wilco,
> -----Original Message-----
> From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
> Sent: Monday, November 6, 2023 12:13 PM
> To: GCC Patches <gcc-patches@gcc.gnu.org>; Richard Sandiford
> <Richard.Sandiford@arm.com>
> Cc: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
> Subject: Re: [PATCH] libatomic: Improve ifunc selection on AArch64
>
>
>
> ping
>
>
> From: Wilco Dijkstra
> Sent: 04 August 2023 16:05
> To: GCC Patches <gcc-patches@gcc.gnu.org>; Richard Sandiford
> <Richard.Sandiford@arm.com>
> Cc: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
> Subject: [PATCH] libatomic: Improve ifunc selection on AArch64
>
>
> Add support for ifunc selection based on CPUID register. Neoverse N1
> supports
> atomic 128-bit load/store, so use the FEAT_USCAT ifunc like newer Neoverse
> cores.
>
> Passes regress, OK for commit?
>
> libatomic/
> config/linux/aarch64/host-config.h (ifunc1): Use CPUID in ifunc
> selection.
>
> ---
>
> diff --git a/libatomic/config/linux/aarch64/host-config.h
> b/libatomic/config/linux/aarch64/host-config.h
> index
> 851c78c01cd643318aaa52929ce4550266238b79..e5dc33c030a4bab927874fa6
> c69425db463fdc4b 100644
> --- a/libatomic/config/linux/aarch64/host-config.h
> +++ b/libatomic/config/linux/aarch64/host-config.h
> @@ -26,7 +26,7 @@
>
> #ifdef HWCAP_USCAT
> # if N == 16
> -# define IFUNC_COND_1 (hwcap & HWCAP_USCAT)
> +# define IFUNC_COND_1 ifunc1 (hwcap)
> # else
> # define IFUNC_COND_1 (hwcap & HWCAP_ATOMICS)
> # endif
> @@ -50,4 +50,28 @@
> #undef MAYBE_HAVE_ATOMIC_EXCHANGE_16
> #define MAYBE_HAVE_ATOMIC_EXCHANGE_16 1
>
> +#ifdef HWCAP_USCAT
> +
> +#define MIDR_IMPLEMENTOR(midr) (((midr) >> 24) & 255)
> +#define MIDR_PARTNUM(midr) (((midr) >> 4) & 0xfff)
> +
> +static inline bool
> +ifunc1 (unsigned long hwcap)
> +{
> + if (hwcap & HWCAP_USCAT)
> + return true;
> + if (!(hwcap & HWCAP_CPUID))
> + return false;
> +
> + unsigned long midr;
> + asm volatile ("mrs %0, midr_el1" : "=r" (midr));
From what I recall that midr_el1 register is emulated by the kernel and so userspace software has to check that the kernel supports that emulation through hwcaps before reading it.
According to https://www.kernel.org/doc/html/v5.8/arm64/cpu-feature-registers.html you need to check getauxval(AT_HWCAP) & HWCAP_CPUID) before doing that read.
Thanks,
Kyrill
> +
> + /* Neoverse N1 supports atomic 128-bit load/store. */
> + if (MIDR_IMPLEMENTOR (midr) == 'A' && MIDR_PARTNUM(midr) == 0xd0c)
> + return true;
> +
> + return false;
> +}
> +#endif
> +
> #include_next <host-config.h>
next prev parent reply other threads:[~2023-11-10 10:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 15:05 Wilco Dijkstra
2023-08-10 2:11 ` Richard Henderson
2023-08-10 2:15 ` Richard Henderson
2023-08-10 9:50 ` Wilco Dijkstra
2023-08-10 15:14 ` Richard Henderson
2023-08-10 16:09 ` Wilco Dijkstra
2023-09-13 14:56 ` Wilco Dijkstra
2023-10-16 12:51 ` Wilco Dijkstra
2023-11-06 12:12 ` Wilco Dijkstra
2023-11-10 10:00 ` Kyrylo Tkachov [this message]
2023-11-10 10:22 ` Wilco Dijkstra
2023-11-10 12:36 ` Kyrylo Tkachov
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=PAXPR08MB69260BD4D15052B0B852B93393AEA@PAXPR08MB6926.eurprd08.prod.outlook.com \
--to=kyrylo.tkachov@arm.com \
--cc=Richard.Sandiford@arm.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).