From: ard.biesheuvel@linaro.org (Ard Biesheuvel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] arm64: use subsections instead of function calls for LL/SC fallbacks
Date: Tue, 13 Nov 2018 15:39:20 -0800 [thread overview]
Message-ID: <20181113233923.20098-1-ard.biesheuvel@linaro.org> (raw)
Refactor the LL/SC atomics code so we can emit the LL/SC fallbacks for the
LSE atomics as subsections that get instantiated at each call site rather
than as out of line functions that get called from inline asm (without the
awareness of the compiler)
This should allow slightly better LSE code, and removes stack spilling and
potential PLT indirection for the LL/SC fallbacks.
Ard Biesheuvel (3):
arm64/atomics: refactor LL/SC base asm templates
arm64/atomics: use subsections for out of line LL/SC alternatives
arm64/atomics: remove out of line LL/SC alternatives
arch/arm64/include/asm/atomic_ll_sc.h | 190 ++++---
arch/arm64/include/asm/atomic_lse.h | 558 ++++++++++----------
arch/arm64/include/asm/lse.h | 13 -
arch/arm64/lib/Makefile | 19 -
arch/arm64/lib/atomic_ll_sc.c | 3 -
5 files changed, 372 insertions(+), 411 deletions(-)
delete mode 100644 arch/arm64/lib/atomic_ll_sc.c
--
2.17.1
next reply other threads:[~2018-11-13 23:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 23:39 Ard Biesheuvel [this message]
2018-11-13 23:39 ` [PATCH 1/3] arm64/atomics: refactor LL/SC base asm templates Ard Biesheuvel
2018-11-13 23:39 ` [PATCH 2/3] arm64/atomics: use subsections for out of line LL/SC alternatives Ard Biesheuvel
2018-11-13 23:39 ` [PATCH 3/3] arm64/atomics: remove " Ard Biesheuvel
2018-11-27 19:30 ` [PATCH 0/3] arm64: use subsections instead of function calls for LL/SC fallbacks Will Deacon
2018-11-28 9:16 ` Ard Biesheuvel
2018-11-28 9:33 ` Ard Biesheuvel
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=20181113233923.20098-1-ard.biesheuvel@linaro.org \
--to=ard.biesheuvel@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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 NNTP newsgroup(s).