From: Thomas Richter <tmricht@linux.ibm.com>
To: James Clark <james.clark@linaro.org>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
acme@kernel.org, namhyung@kernel.org, svens@linux.ibm.com
Cc: agordeev@linux.ibm.com, gor@linux.ibm.com,
sumanthk@linux.ibm.com, hca@linux.ibm.com
Subject: Re: [PING PATCH] perf/test: fix perf ftrace test on s390
Date: Thu, 14 Nov 2024 16:34:06 +0100 [thread overview]
Message-ID: <ae0f7492-412b-4506-9127-514577b33e7e@linux.ibm.com> (raw)
In-Reply-To: <b107d9a6-48b7-468d-b36e-da9c587b7953@linaro.org>
On 11/14/24 12:09, James Clark wrote:
>
>
> On 14/11/2024 9:01 am, Thomas Richter wrote:
>> On s390 the perf test case ftrace sometimes fails as follows:
>>
>> # ./perf test ftrace
>> 79: perf ftrace tests : FAILED!
>> #
>>
>> The failure depends on the kernel .config file. Some configurarions
>> always work fine, some do not. The ftrace profile test mostly fails,
>> because the ring buffer was not large enough, and some lines
>> (especially the interesting ones with nanosleep in it) where dropped.
>>
>> To achieve success for all our tested kernel configurations, enlarge
>> the buffer to store the traces complete without wrapping.
>> The default buffer size is too small for all kernel configurations.
>> Set the buffer size of /sys/kernel/tracing/buffer_size_kb to 16 MB
>>
>>
>> Output after:
>> # ./perf test ftrace
>> 79: perf ftrace tests : Ok
>> #
>>
>> Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
>> Suggested-by: Sven Schnelle <svens@linux.ibm.com>
>> ---
>> tools/perf/tests/shell/ftrace.sh | 11 +++++++++++
>> 1 file changed, 11 insertions(+)
>>
>> diff --git a/tools/perf/tests/shell/ftrace.sh b/tools/perf/tests/shell/ftrace.sh
>> index a6ee740f0d7e..742d6b8f34d3 100755
>> --- a/tools/perf/tests/shell/ftrace.sh
>> +++ b/tools/perf/tests/shell/ftrace.sh
>> @@ -80,10 +80,21 @@ test_ftrace_profile() {
>> echo "perf ftrace profile test [Success]"
>> }
>> +if [ "$(uname -m)" = "s390x" ]
>> +then
>> + ftrace_size=$(cat /sys/kernel/tracing/buffer_size_kb)
>> + echo 16384 > /sys/kernel/tracing/buffer_size_kb
>> +fi
>> +
>
> It probably wouldn't be terrible to do this for all platforms to reduce fragmentation. It doesn't do any harm and it only added a few seconds to the test time even on a small Arm box, maybe it will prevent flakes everywhere else in the future. But I don't feel too strongly about this one.
>
>> test_ftrace_list
>> test_ftrace_trace
>> test_ftrace_latency
>> test_ftrace_profile
>> +if [ "$(uname -m)" = "s390x" ]
>> +then
>> + echo $ftrace_size > /sys/kernel/tracing/buffer_size_kb
>> +fi
>> +
>
> Restoring the value should be in cleanup() so it works on interrupt too.
>
> With that:
>
> Reviewed-by: James Clark <james.clark@linaro.org>
>
Thanks for your feedback. Will do it and post v2
--
Thomas Richter, Dept 3303, IBM s390 Linux Development, Boeblingen, Germany
--
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Wolfgang Wendt
Geschäftsführung: David Faller
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294
prev parent reply other threads:[~2024-11-14 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 9:01 [PING PATCH] perf/test: fix perf ftrace test on s390 Thomas Richter
2024-11-14 11:09 ` James Clark
2024-11-14 15:34 ` Thomas Richter [this message]
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=ae0f7492-412b-4506-9127-514577b33e7e@linux.ibm.com \
--to=tmricht@linux.ibm.com \
--cc=acme@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=james.clark@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=sumanthk@linux.ibm.com \
--cc=svens@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).