From: Andreas Larsson <andreas@gaisler.com>
To: Rosen Penev <rosenp@gmail.com>, sparclinux@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
open list <linux-kernel@vger.kernel.org>,
"open list:CLANG/LLVM BUILD SUPPORT:Keyword:b(?i:clang|llvm)b"
<llvm@lists.linux.dev>
Subject: Re: [PATCH] sparc: Export mcount for Clang-built modules
Date: Fri, 12 Jun 2026 11:28:45 +0200 [thread overview]
Message-ID: <9a48cc07-0ead-453b-99e6-ff1980e52381@gaisler.com> (raw)
In-Reply-To: <20260508021119.1635054-1-rosenp@gmail.com>
On 2026-05-08 04:11, Rosen Penev wrote:
> Clang emits calls to mcount for -pg on sparc64, while the
> existing ftrace support only exports the _mcount name. With
> FUNCTION_TRACER enabled, modules can therefore keep relocations
> against mcount and fail during modpost:
>
> ERROR: modpost: "mcount" [arch/sparc/kernel/chmc.ko] undefined!
>
> _mcount and mcount are aliases in arch/sparc/lib/mcount.S. Export
> the plain mcount alias as well so Clang-built modules can resolve
> their profiling call target.
>
> Assisted-by: Codex:GPT-5
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
> ---
> arch/sparc/lib/mcount.S | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/sparc/lib/mcount.S b/arch/sparc/lib/mcount.S
> index f7f7910eb41e..0309ba2c4712 100644
> --- a/arch/sparc/lib/mcount.S
> +++ b/arch/sparc/lib/mcount.S
> @@ -21,6 +21,7 @@
> EXPORT_SYMBOL(_mcount)
> .globl mcount
> .type mcount,#function
> + EXPORT_SYMBOL(mcount)
> _mcount:
> mcount:
> #ifdef CONFIG_FUNCTION_TRACER
Hi,
Please also add it to arch/sparc/include/asm/asm-prototypes.h, like in
https://lore.kernel.org/sparclinux/20260523042535.C3A6B1F000E9@smtp.kernel.org
to not get an added warning about mcount in modpost.
Thanks,
Andreas
prev parent reply other threads:[~2026-06-12 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 2:11 Rosen Penev
2026-06-12 9:28 ` Andreas Larsson [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=9a48cc07-0ead-453b-99e6-ff1980e52381@gaisler.com \
--to=andreas@gaisler.com \
--cc=davem@davemloft.net \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=rosenp@gmail.com \
--cc=sparclinux@vger.kernel.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
all inboxes | Powered by JetHome®