summaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/bin
diff options
context:
space:
mode:
authorHari Bathini <hbathini@linux.ibm.com>2026-01-27 14:19:26 +0530
committerMadhavan Srinivasan <maddy@linux.ibm.com>2026-03-07 16:02:25 +0530
commitdb54c28702f7270e74dce36c84cb0db4cec96389 (patch)
treebdfdcd8bbd2eebe0f24c9f9b0e3f920ce051c181 /tools/perf/scripts/python/bin
parent875612a7745013a43c67493cb0583ee3f7476344 (diff)
downloadlinux-db54c28702f7270e74dce36c84cb0db4cec96389.tar.gz
linux-db54c28702f7270e74dce36c84cb0db4cec96389.zip
powerpc64/ftrace: workaround clang recording GEP in __patchable_function_entries
Support for -fpatchable-function-entry on ppc64le was added in Clang with [1]. However, when no prefix NOPs are specified - as is the case with CONFIG_PPC_FTRACE_OUT_OF_LINE - the first NOP is emitted at LEP, but Clang records the Global Entry Point (GEP) unlike GCC which does record the Local Entry Point (LEP). Issue [2] has been raised to align Clang's behavior with GCC. As a temporary workaround to ensure ftrace initialization works as expected with Clang, derive the LEP using ppc_function_entry() for kernel symbols and by looking for the below module GEP sequence for module addresses, until [2] is resolved: ld r2, -8(r12) add r2, r2, r12 [1] https://github.com/llvm/llvm-project/pull/151569 [2] https://github.com/llvm/llvm-project/issues/163706 Signed-off-by: Hari Bathini <hbathini@linux.ibm.com> Tested-by: Venkat Rao Bagalkote <venkat88@linux.ibm.com> Signed-off-by: Madhavan Srinivasan <maddy@linux.ibm.com> Link: https://patch.msgid.link/20260127084926.34497-4-hbathini@linux.ibm.com
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions