From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>, <linuxppc-dev@ozlabs.org>
Cc: duwe@lst.de, aneesh.kumar@linux.vnet.ibm.com,
Anton Blanchard <anton@samba.org>
Subject: Re: [2/2] powerpc/modules: Never restore r2 for a mprofile-kernel style mcount() call
Date: Fri, 22 Jul 2016 15:50:43 +1000 (AEST) [thread overview]
Message-ID: <3rwfrg24k8z9t0d@ozlabs.org> (raw)
In-Reply-To: <1468903711-5869-2-git-send-email-mpe@ellerman.id.au>
On Tue, 2016-19-07 at 04:48:31 UTC, Michael Ellerman wrote:
> In the module loader we process relocations, and for long jumps we
> generate trampolines (aka stubs). At the call site for one of these
> trampolines we usually need to generate a load instruction to restore
> the TOC pointer into r2.
...
>
> The fix is relatively simple, in restore_r2() we check for an
> mprofile-kernel style mcount() call first, before looking for the
> presence of a nop.
>
> Fixes: 153086644fd1 ("powerpc/ftrace: Add support for -mprofile-kernel ftrace ABI")
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Applied to powerpc next.
https://git.kernel.org/powerpc/c/31278b17a0dfed3014786b623f
cheers
next prev parent reply other threads:[~2016-07-22 5:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 4:48 [PATCH 1/2] powerpc/ftrace: Separate the heuristics for checking call sites Michael Ellerman
2016-07-19 4:48 ` [PATCH 2/2] powerpc/modules: Never restore r2 for a mprofile-kernel style mcount() call Michael Ellerman
2016-07-22 5:50 ` Michael Ellerman [this message]
2016-07-19 5:44 ` [PATCH 1/2] powerpc/ftrace: Separate the heuristics for checking call sites Madhavan Srinivasan
2016-07-21 10:36 ` Michael Ellerman
2016-07-22 5:50 ` [1/2] " Michael Ellerman
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=3rwfrg24k8z9t0d@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=anton@samba.org \
--cc=duwe@lst.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.