From: Steven Rostedt <rostedt@goodmis.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Mark Rutland <mark.rutland@arm.com>,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] ftrace/selftest: Test combination of function_graph tracer and function profiler
Date: Thu, 22 Aug 2024 09:19:29 -0400 [thread overview]
Message-ID: <20240822091929.0db8837f@gandalf.local.home> (raw)
In-Reply-To: <3901c521-be69-4824-a571-9182b9af02b6@linuxfoundation.org>
On Wed, 21 Aug 2024 21:54:42 -0600
Shuah Khan <skhan@linuxfoundation.org> wrote:
> On 8/21/24 13:09, Steven Rostedt wrote:
> > From: Steven Rostedt <rostedt@goodmis.org>
> >
> > Masami reported a bug when running function graph tracing then the
> > function profiler. The following commands would cause a kernel crash:
> >
> > # cd /sys/kernel/tracing/
> > # echo function_graph > current_tracer
> > # echo 1 > function_profile_enabled
> >
> > In that order. Create a test to test this two to make sure this does not
> > come back as a regression.
> >
> > Link: https://lore.kernel.org/172398528350.293426.8347220120333730248.stgit@devnote2
> >
> > Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> > ---
> > .../ftrace/test.d/ftrace/fgraph-profiler.tc | 30 +++++++++++++++++++
> > 1 file changed, 30 insertions(+)
> > create mode 100644 tools/testing/selftests/ftrace/test.d/ftrace/fgraph-profiler.tc
> >
> > diff --git a/tools/testing/selftests/ftrace/test.d/ftrace/fgraph-profiler.tc b/tools/testing/selftests/ftrace/test.d/ftrace/fgraph-profiler.tc
> > new file mode 100644
> > index 000000000000..62d44a1395da
> > --- /dev/null
> > +++ b/tools/testing/selftests/ftrace/test.d/ftrace/fgraph-profiler.tc
> > @@ -0,0 +1,30 @@
> > +#!/bin/sh
> > +# SPDX-License-Identifier: GPL-2.0
> > +# description: ftrace - function profiler with function graph tracing
> > +# requires: function_profile_enabled set_ftrace_filter function_graph:tracer
> > +
> > +# The function graph tracer can now be run along side of the function
> > +# profiler. But there was a bug that caused the combination of the two
> > +# to crash. It also required the function graph tracer to be started
> > +# first.
> > +#
> > +# This test triggers that bug
> > +#
> > +# We need function_graph and profiling to to run this test
> > +
> > +fail() { # mesg
> > + echo $1
> > + exit_fail
> > +}
> > +
> > +echo "Enabling function graph tracer:"
> > +echo function_graph > current_tracer
> > +echo "enable profiler"
> > +
> > +# Older kernels do not allow function_profile to be enabled with
> > +# function graph tracer. If the below fails, mark it as unsupported
> > +echo 1 > function_profile_enabled || exit_unsupported
> > +
> > +sleep 1
>
> Any specific reason for this sleep 1 - can you add a comment on top?
We add sleep 1 in several locations of the ftrace selftests to let the
tracing run for a bit just to see if it triggers anything. Otherwise the
clean up can happen before anything gets traced. Although, it's highly
unlikely in this case, but still.
I could add a comment if you want of just:
# let it run for a bit
sleep 1
> > +
> > +exit 0
>
> Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
>
> Let me know if you would like v2 for this to be taken through my tree.
I'll make a v2 if you want me to.
-- Steve
next prev parent reply other threads:[~2024-08-22 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 19:09 [PATCH] ftrace/selftest: Test combination of function_graph tracer and function profiler Steven Rostedt
2024-08-22 3:54 ` Shuah Khan
2024-08-22 13:19 ` Steven Rostedt [this message]
2024-08-26 13:53 ` Shuah Khan
2024-08-25 15:14 ` 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=20240822091929.0db8837f@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).