From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ftrace bug
Date: Mon, 7 Mar 2022 13:00:05 +0100 [thread overview]
Message-ID: <8bf3ddb5-e9fc-dcc9-ad7d-1677334f6386@broadcom.com> (raw)
In-Reply-To: <9a86b2c9-1009-1683-442e-61c5a7dc8cf3@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 626 bytes --]
On 3/7/2022 12:26 PM, Arend van Spriel wrote:
> Hi Steven,
>
> I wanted to use FTRACE on an ARM platform and I hit the following
> warning which results in ftrace bug. This happens upon loading a module.
> Looking up the warning I suspect the branch target is too far off. The
> module is quite large and therefor not loaded in the modules section. Is
> there a way to exclude a module. In ftrace_module_init I see a check for
> !mod->num_ftrace_callsites. Is there a way to avoid creating ftrace
> callsites in a module?
Could it be accomplished by this?
CFLAGS_REMOVE_lockdep.o = $(CC_FLAGS_FTRACE)
Regards,
Arend
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4219 bytes --]
next prev parent reply other threads:[~2022-03-07 12:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 11:26 Arend van Spriel
2022-03-07 12:00 ` Arend van Spriel [this message]
2022-03-07 13:28 ` Steven Rostedt
2022-03-07 13:24 ` Steven Rostedt
2022-03-08 10:53 ` Arend van Spriel
2022-03-08 15:20 ` Steven Rostedt
2022-03-08 16:02 ` Alexander Sverdlin
2022-03-08 17:29 ` Arend Van Spriel
2022-03-08 17:45 ` Steven Rostedt
2022-03-08 18:14 ` Arend Van Spriel
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=8bf3ddb5-e9fc-dcc9-ad7d-1677334f6386@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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
all inboxes | Powered by JetHome®