summaryrefslogtreecommitdiff
path: root/arch/powerpc/kernel/module_64.c
diff options
context:
space:
mode:
authorMichael Ellerman <mpe@ellerman.id.au>2016-07-19 07:48:30 +0300
committerMichael Ellerman <mpe@ellerman.id.au>2016-07-21 13:10:37 +0300
commit9d636109511a000882f8dff4eaafa874eec5ece8 (patch)
tree321f23e7a84c48b008f5996238d67e6db1dc07fd /arch/powerpc/kernel/module_64.c
parentb1923caa6e641f3d0a93b5d045aef67ded5aef67 (diff)
downloadlinux-9d636109511a000882f8dff4eaafa874eec5ece8.tar.xz
powerpc/ftrace: Separate the heuristics for checking call sites
In __ftrace_make_nop() (the 64-bit version), we have code to deal with two ftrace ABIs. There is the original ABI, which looks mostly like a function call, and then the mprofile-kernel ABI which is just a branch. The code tries to handle both cases, by looking for the presence of a load to restore the TOC pointer (PPC_INST_LD_TOC). If we detect the TOC load, we assume the call site is for an mcount() call using the old ABI. That means we patch the mcount() call with a b +8, to branch over the TOC load. However if the kernel was built with mprofile-kernel, then there will never be a call site using the original ftrace ABI. If for some reason we do see a TOC load, then it's there for a good reason, and we should not jump over it. So split the code, using the existing CC_USING_MPROFILE_KERNEL. Kernels built with mprofile-kernel will only look for, and expect, the new ABI, and similarly for the original ABI. Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'arch/powerpc/kernel/module_64.c')
0 files changed, 0 insertions, 0 deletions