From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: "naohirot@fujitsu.com" <naohirot@fujitsu.com>
Cc: 'GNU C Library' <libc-alpha@sourceware.org>,
Szabolcs Nagy <Szabolcs.Nagy@arm.com>
Subject: Re: [PATCH 0/5] Added optimized memcpy/memmove/memset for A64FX
Date: Thu, 6 May 2021 17:31:26 +0000 [thread overview]
Message-ID: <VE1PR08MB5599A02061BAB1A9B81FFDAE83589@VE1PR08MB5599.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <TYAPR01MB6025DC532F3C09A0E121188CDF589@TYAPR01MB6025.jpnprd01.prod.outlook.com>
Hi Naohiro,
> I've read the mail thread regarding BTI, but I think I couldn't fully understand the
> problem. BTI seems available from ARMv8.5, and A64FX is ARMv8.2.
BTI instructions are NOP hints, so it is possible to enable BTI even on ARMv8.0.
Using BTI instructions is harmless on CPUs that don't support it if NOP hints are as
cheap as a NOP (which generally doesn't need any execution resources).
> Even though distro distributed BTI enabled binary, BTI doesn't work on A64FX.
It works (ie. it is binary compatible with A64FX) and should have no effect. However
it seems to cause an unexpected slowdown.
> So BTI_J macro can be removed from A64FX IFUNC code at least, because A64FX
> IFUNC code is executed only on A64FX.
How is removing it just from memcpy going to help? The worry is not about memcpy
but the slowdown from all the BTI instructions that will be added to most functions.
Note it is still worthwhile to change BTI_C to NOP as suggested - that is the case when
BTI is not enabled, and there you want to avoid inserting BTI when it is not needed.
Cheers,
Wilco
next prev parent reply other threads:[~2021-05-06 17:31 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 12:52 Wilco Dijkstra
2021-04-12 18:53 ` Florian Weimer
2021-04-13 12:07 ` naohirot
2021-04-14 16:02 ` Wilco Dijkstra
2021-04-15 12:20 ` naohirot
2021-04-20 16:00 ` Wilco Dijkstra
2021-04-27 11:58 ` naohirot
2021-04-29 15:13 ` Wilco Dijkstra
2021-04-30 15:01 ` Szabolcs Nagy
2021-04-30 15:23 ` Wilco Dijkstra
2021-04-30 15:30 ` Florian Weimer
2021-04-30 15:40 ` Wilco Dijkstra
2021-05-04 7:56 ` Szabolcs Nagy
2021-05-04 10:17 ` Florian Weimer
2021-05-04 10:38 ` Wilco Dijkstra
2021-05-04 10:42 ` Szabolcs Nagy
2021-05-04 11:07 ` Florian Weimer
2021-05-06 10:01 ` naohirot
2021-05-06 14:26 ` Szabolcs Nagy
2021-05-06 15:09 ` Florian Weimer
2021-05-06 17:31 ` Wilco Dijkstra [this message]
2021-05-07 12:31 ` naohirot
2021-04-19 2:51 ` naohirot
2021-04-19 14:57 ` Wilco Dijkstra
2021-04-21 10:10 ` naohirot
2021-04-21 15:02 ` Wilco Dijkstra
2021-04-22 13:17 ` naohirot
2021-04-23 0:58 ` naohirot
2021-04-19 12:43 ` naohirot
2021-04-20 3:31 ` naohirot
2021-04-20 14:44 ` Wilco Dijkstra
2021-04-27 9:01 ` naohirot
2021-04-20 5:49 ` naohirot
2021-04-20 11:39 ` Wilco Dijkstra
2021-04-27 11:03 ` naohirot
2021-04-23 13:22 ` naohirot
-- strict thread matches above, loose matches on Subject: below --
2021-03-17 2:28 Naohiro Tamura
2021-03-29 12:03 ` Szabolcs Nagy
2021-05-10 1:45 ` naohirot
2021-05-14 13:35 ` Szabolcs Nagy
2021-05-19 0:11 ` naohirot
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=VE1PR08MB5599A02061BAB1A9B81FFDAE83589@VE1PR08MB5599.eurprd08.prod.outlook.com \
--to=wilco.dijkstra@arm.com \
--cc=Szabolcs.Nagy@arm.com \
--cc=libc-alpha@sourceware.org \
--cc=naohirot@fujitsu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).