From: Daniel Wagner <dwagner@suse.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-kernel@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: kprobe not always triggering
Date: Wed, 15 Jan 2025 17:50:40 +0100 [thread overview]
Message-ID: <03179c0c-5133-440c-8072-945601d39e5b@flourine.local> (raw)
In-Reply-To: <20250115113733.650db5c0@gandalf.local.home>
On Wed, Jan 15, 2025 at 11:37:33AM -0500, Steven Rostedt wrote:
> Grumble. I expect this issue to come up more often. We need a way to detect
> this. Come to think of it, I believe this is more of a clang "feature". As
> I do recall some of the other reports were from the clang compiler as well.
clang doesn't seem to offer a more fine grained way to control the
inline decisions. There is no '--inline-all-or-nothing' option.
clang version 19.1.5 (Fedora 19.1.5-1.fc41)
Target: x86_64-redhat-linux-gnu
next prev parent reply other threads:[~2025-01-15 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 8:26 kprobe not always triggering Daniel Wagner
2025-01-15 15:17 ` Steven Rostedt
2025-01-15 16:29 ` Daniel Wagner
2025-01-15 16:37 ` Steven Rostedt
2025-01-15 16:50 ` Daniel Wagner [this message]
2025-01-15 23:48 ` Masami Hiramatsu
2025-01-16 12:04 ` Daniel Wagner
2025-01-17 8:52 ` Masami Hiramatsu
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=03179c0c-5133-440c-8072-945601d39e5b@flourine.local \
--to=dwagner@suse.de \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@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