From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Hari Bathini <hbathini@linux.ibm.com>
Cc: "Naveen N. Rao" <naveen@kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>,
linux-trace-kernel@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
llvm@lists.linux.dev, Maryam Moghadas <maryammo@ca.ibm.com>,
Christophe Leroy <chleroy@kernel.org>
Subject: Re: [PATCH v2 0/3] powerpc64/ftrace: fixes clang build issues
Date: Wed, 11 Mar 2026 07:43:56 +0530 [thread overview]
Message-ID: <177319508343.269267.4001049522671602586.b4-ty@linux.ibm.com> (raw)
In-Reply-To: <20260127084926.34497-1-hbathini@linux.ibm.com>
On Tue, 27 Jan 2026 14:19:23 +0530, Hari Bathini wrote:
> Support for -fpatchable-function-entry on ppc64le was added in Clang
> with [1]. Faced a couple of issues while building the linux kernel
> with Clang though. Patches 1 & 2 address those issues. The last patch
> provides workaround to ensure, an open issue [2] in Clang with
> -fpatchable-function-entry support, does not impact the linux
> ftrace subsystem.
>
> [...]
Applied to powerpc/fixes.
[1/3] powerpc64: make clang cross-build friendly
https://git.kernel.org/powerpc/c/73cdf24e81e4eba52a40a6b10c6cf285d0ac23fd
[2/3] powerpc64/ftrace: fix OOL stub count with clang
https://git.kernel.org/powerpc/c/875612a7745013a43c67493cb0583ee3f7476344
[3/3] powerpc64/ftrace: workaround clang recording GEP in __patchable_function_entries
https://git.kernel.org/powerpc/c/db54c28702f7270e74dce36c84cb0db4cec96389
cheers
prev parent reply other threads:[~2026-03-11 2:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 8:49 [PATCH v2 0/3] powerpc64/ftrace: fixes clang build issues Hari Bathini
2026-01-27 8:49 ` [PATCH v2 1/3] powerpc64: make clang cross-build friendly Hari Bathini
2026-01-27 8:49 ` [PATCH v2 2/3] powerpc64/ftrace: fix OOL stub count with clang Hari Bathini
2026-01-27 8:49 ` [PATCH v2 3/3] powerpc64/ftrace: workaround clang recording GEP in __patchable_function_entries Hari Bathini
2026-01-30 6:18 ` [PATCH v2 0/3] powerpc64/ftrace: fixes clang build issues Venkat Rao Bagalkote
2026-03-11 2:13 ` Madhavan Srinivasan [this message]
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=177319508343.269267.4001049522671602586.b4-ty@linux.ibm.com \
--to=maddy@linux.ibm.com \
--cc=chleroy@kernel.org \
--cc=hbathini@linux.ibm.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=llvm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=maryammo@ca.ibm.com \
--cc=mhiramat@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=rostedt@goodmis.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