From: Steven Rostedt <rostedt@goodmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Yuanhe Shu <xiangzao@linux.alibaba.com>,
Shuah Khan <shuah@kernel.org>,
mathieu.desnoyers@efficios.com, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, stable@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2] selftests/ftrace: Limit length in subsystem-enable tests
Date: Mon, 26 Feb 2024 11:59:42 -0500 [thread overview]
Message-ID: <20240226115942.1213cff4@gandalf.local.home> (raw)
In-Reply-To: <20240226150938.7f0d8fd639bab79199d8556b@kernel.org>
On Mon, 26 Feb 2024 15:09:38 +0900
Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:
> On Mon, 26 Feb 2024 11:18:16 +0800
> Yuanhe Shu <xiangzao@linux.alibaba.com> wrote:
>
> > While sched* events being traced and sched* events continuously happen,
> > "[xx] event tracing - enable/disable with subsystem level files" would
> > not stop as on some slower systems it seems to take forever.
> > Select the first 100 lines of output would be enough to judge whether
> > there are more than 3 types of sched events.
>
> Looks good to me.
>
> Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
>
> Hi Shuah, can you pick this as a fix?
>
Yes please.
Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org>
-- Steve
next prev parent reply other threads:[~2024-02-26 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 3:18 [PATCH v2] selftests/ftrace: Limit length in subsystem-enable tests Yuanhe Shu
2024-02-26 6:09 ` Masami Hiramatsu
2024-02-26 16:59 ` Steven Rostedt [this message]
2024-04-04 16:29 ` Shuah Khan
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=20240226115942.1213cff4@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=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=xiangzao@linux.alibaba.com \
/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