From: Yuanhe Shu <xiangzao@linux.alibaba.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Shuah Khan <skhan@linuxfoundation.org>
Cc: mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
shuah@kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] selftests/ftrace: Limit length in subsystem-enable tests
Date: Thu, 22 Feb 2024 20:14:56 +0800 [thread overview]
Message-ID: <7420f9b5-2283-419f-8c6b-705f8b0c53f6@linux.alibaba.com> (raw)
In-Reply-To: <20240205082120.4144fb6f@rorschach.local.home>
On 2024/2/5 21:21, Steven Rostedt wrote:
> On Mon, 5 Feb 2024 21:12:33 +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
>> never stop as it cat an endless output.
>> Select the first 100 lines of output would be enough to judge whether
>> there are more than 3 types of sched events.
>
> It's not that it never stops but on some slower systems it does seem to
> take forever.
>
> Acked-by: Steven Rostedt (Google) <rostedt@org>
>
> Shuah,
>
> Can you take this through your tree?
>
> Thanks,
>
> -- Steve
>
Thanks for your ack but I found that I missed the 2nd and 3rd 'trace'
after 'head -n 100' in code. Should I resend a new patch to fix this and
meanwhile modify commit messages according to Steve's words?
>
>>
>> Signed-off-by: Yuanhe Shu <xiangzao@linux.alibaba.com>
>> ---
>> .../selftests/ftrace/test.d/event/subsystem-enable.tc | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/tools/testing/selftests/ftrace/test.d/event/subsystem-enable.tc b/tools/testing/selftests/ftrace/test.d/event/subsystem-enable.tc
>> index b1ede6249866..74c1114603a7 100644
>> --- a/tools/testing/selftests/ftrace/test.d/event/subsystem-enable.tc
>> +++ b/tools/testing/selftests/ftrace/test.d/event/subsystem-enable.tc
>> @@ -18,7 +18,7 @@ echo 'sched:*' > set_event
>>
>> yield
>>
>> -count=`cat trace | grep -v ^# | awk '{ print $5 }' | sort -u | wc -l`
>> +count=`head -n 100 trace | grep -v ^# | awk '{ print $5 }' | sort -u | wc -l`
>> if [ $count -lt 3 ]; then
>> fail "at least fork, exec and exit events should be recorded"
>> fi
>> @@ -29,7 +29,7 @@ echo 1 > events/sched/enable
>>
>> yield
>>
>> -count=`cat trace | grep -v ^# | awk '{ print $5 }' | sort -u | wc -l`
>> +count=`head -n 100 | grep -v ^# | awk '{ print $5 }' | sort -u | wc -l`
>> if [ $count -lt 3 ]; then
>> fail "at least fork, exec and exit events should be recorded"
>> fi
>> @@ -40,7 +40,7 @@ echo 0 > events/sched/enable
>>
>> yield
>>
>> -count=`cat trace | grep -v ^# | awk '{ print $5 }' | sort -u | wc -l`
>> +count=`head -n 100 | grep -v ^# | awk '{ print $5 }' | sort -u | wc -l`
>> if [ $count -ne 0 ]; then
>> fail "any of scheduler events should not be recorded"
>> fi
next prev parent reply other threads:[~2024-02-22 12:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240205131233.13686-1-xiangzao@linux.alibaba.com>
2024-02-05 13:21 ` [PATCH] selftests/ftrace: Limit length in subsystem-enable tests Steven Rostedt
2024-02-22 12:14 ` Yuanhe Shu [this message]
2024-02-25 22:30 ` 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=7420f9b5-2283-419f-8c6b-705f8b0c53f6@linux.alibaba.com \
--to=xiangzao@linux.alibaba.com \
--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=rostedt@goodmis.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