mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Heiko Carstens <hca@linux.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Sven Schnelle <svens@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>
Subject: Re: [GIT PULL] ftrace: Updates for v6.14
Date: Mon, 17 Feb 2025 12:49:18 +0100	[thread overview]
Message-ID: <20250217114918.10397-A-hca@linux.ibm.com> (raw)
In-Reply-To: <20250119193134.0ebd56bc@gandalf.local.home>

Hi Steven, Masami,

On Sun, Jan 19, 2025 at 07:31:34PM -0500, Steven Rostedt wrote:
> ftrace updates for v6.14:
> 
> - Have fprobes built on top of function graph infrastructure

this seems to cause a regression:

When I run tools/testing/selftests/ftrace/ftracetest I now end up with all
functions being enabled for ftrace after the test suite ran:

$ wc -l /sys/kernel/debug/tracing/enabled_functions
50779 /sys/kernel/debug/tracing/enabled_functions

$ cat /sys/kernel/debug/tracing/enabled_functions
...
down (1)           
down_interruptible (1)           
down_killable (1)           

$ cat /sys/kernel/debug/tracing/current_tracer
nop

Bisected to commit 4346ba160409 ("fprobe: Rewrite fprobe on function-graph
tracer"). Before this commit there were no ftrace enabled functions after the
test suite finished:

$ wc -l /sys/kernel/debug/tracing/enabled_functions
0 /sys/kernel/debug/tracing/enabled_functions

This is on s390 with defconfig.

  parent reply	other threads:[~2025-02-17 11:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-20  0:31 Steven Rostedt
2025-01-21 23:22 ` pr-tracker-bot
2025-02-17 11:49 ` Heiko Carstens [this message]
2025-02-17 18:38   ` Steven Rostedt
2025-02-18 16:26     ` Steven Rostedt

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=20250217114918.10397-A-hca@linux.ibm.com \
    --to=hca@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=svens@linux.ibm.com \
    --cc=torvalds@linux-foundation.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®