From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail.com>, Alan Modra <amodra@gmail.com>
Subject: [PATCH 0/5] powerpc/64: avoid GOT addressing, don't put data in TOC
Date: Fri, 23 Sep 2022 13:25:07 +1000 [thread overview]
Message-ID: <20220923032512.535725-1-npiggin@gmail.com> (raw)
This is a cleaned up set of the initial prep patches from the pcrel
series, dealing with regularising addressing variables from asm
and using helper macros more consistently.
Nothing really new, this is more complete, splits out the changes
more logically, adds changelog/comments, and avoids touching ppc32
much (only slight comment change and interrupt stack magic number
change).
Patch 2 is probably actually required before we make the TOC readonly
at runtime, because there is one case (hcall_tracepoint_refcount)
that puts read-write data in the TOC section.
Thanks,
Nick
Nicholas Piggin (5):
powerpc/64: use 32-bit immediate for STACK_FRAME_REGS_MARKER
powerpc/64: asm use consistent global variable declaration and access
powerpc/64: switch asm helpers from GOT to TOC relative addressing
powerpc/64: provide a helper macro to load r2 with the kernel TOC
powerpc/64e: provide an addressing macro for use with TOC in alternate
register
arch/powerpc/boot/opal-calls.S | 6 ++--
arch/powerpc/boot/ppc_asm.h | 10 ++++++
arch/powerpc/include/asm/ppc_asm.h | 20 ++++++++++-
arch/powerpc/include/asm/ptrace.h | 5 +--
arch/powerpc/kernel/entry_32.S | 6 ++--
arch/powerpc/kernel/exceptions-64e.S | 34 ++++++++-----------
arch/powerpc/kernel/exceptions-64s.S | 8 ++---
arch/powerpc/kernel/head_64.S | 11 ++----
arch/powerpc/kernel/interrupt_64.S | 28 +++++----------
arch/powerpc/kernel/optprobes_head.S | 2 +-
arch/powerpc/kernel/swsusp_asm64.S | 16 +++------
arch/powerpc/kernel/trace/ftrace_low.S | 2 +-
arch/powerpc/kernel/trace/ftrace_mprofile.S | 6 ++--
arch/powerpc/kernel/vector.S | 15 ++++----
arch/powerpc/kvm/book3s_64_entry.S | 2 +-
arch/powerpc/kvm/book3s_hv_rmhandlers.S | 4 +--
arch/powerpc/kvm/tm.S | 2 +-
arch/powerpc/lib/copypage_64.S | 7 +---
arch/powerpc/lib/string_64.S | 7 +---
arch/powerpc/mm/nohash/tlb_low_64e.S | 4 +--
arch/powerpc/perf/bhrb.S | 2 +-
.../powerpc/platforms/powernv/opal-wrappers.S | 2 +-
arch/powerpc/platforms/pseries/hvCall.S | 4 +--
arch/powerpc/xmon/spr_access.S | 4 +--
24 files changed, 97 insertions(+), 110 deletions(-)
--
2.37.2
next reply other threads:[~2022-09-23 3:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 3:25 Nicholas Piggin [this message]
2022-09-23 3:25 ` [PATCH 1/5] powerpc/64: use 32-bit immediate for STACK_FRAME_REGS_MARKER Nicholas Piggin
2022-09-23 5:34 ` Christophe Leroy
2022-09-23 6:14 ` Nicholas Piggin
2022-09-23 3:25 ` [PATCH 2/5] powerpc/64: asm use consistent global variable declaration and access Nicholas Piggin
2022-09-23 3:25 ` [PATCH 3/5] powerpc/64: switch asm helpers from GOT to TOC relative addressing Nicholas Piggin
2022-09-23 3:25 ` [PATCH 4/5] powerpc/64: provide a helper macro to load r2 with the kernel TOC Nicholas Piggin
2022-09-23 3:25 ` [PATCH 5/5] powerpc/64e: provide an addressing macro for use with TOC in alternate register Nicholas Piggin
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=20220923032512.535725-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=amodra@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.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).