From: Namhyung Kim <namhyung@kernel.org>
To: Thomas Richter <tmricht@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
acme@kernel.org, agordeev@linux.ibm.com, gor@linux.ibm.com,
sumanthk@linux.ibm.com, hca@linux.ibm.com
Subject: Re: [PATCH] perf test: Fix perf test case 84 on s390
Date: Thu, 17 Oct 2024 13:28:31 -0700 [thread overview]
Message-ID: <ZxFzb7LEu9n9piVG@google.com> (raw)
In-Reply-To: <20241015074726.268029-1-tmricht@linux.ibm.com>
Hello,
On Tue, Oct 15, 2024 at 09:47:26AM +0200, Thomas Richter wrote:
> Perf test case 84 'perf pipe recording and injection test'
> sometime fails on s390, especially on z/VM virtual machines.
>
> This is caused by a very short run time of workload
>
> # perf test -w noploop
>
> which runs for 1 second. Occasionally this is not long
> enough and the perf report has no samples for symbol noploop.
>
> Fix this and enlarge the runtime for the perf work load
> to 3 seconds. This ensures the symbol noploop is always
> present.
Hmm.. but it would slow down the test quite a lot. Can you please make
it conditional on s390 or something?
Maybe you could add a fallback logic to increase the period if it fails.
Thanks,
Namhyung
>
> Output before:
> Inject -b build-ids test
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 0.195 MB - ]
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 0.277 MB - ]
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 0.195 MB - ]
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 0.160 MB
> /tmp/perf.data.ELzRdq (4031 samples) ]
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 0.195 MB - ]
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 0.195 MB - ]
> Inject -b build-ids test [Success]
>
> Inject --buildid-all build-ids test
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 0.195 MB - ]
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 0.014 MB - ]
> Inject --buildid-all build-ids test [Failed - cannot find
> noploop function in pipe #2]
>
> Output after:
> Successful execution for over 10 times in a loop.
>
> Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
> Reviewed-by: Sumanth Korikkar <sumanthk@linux.ibm.com>
> ---
> tools/perf/tests/shell/pipe_test.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/tests/shell/pipe_test.sh b/tools/perf/tests/shell/pipe_test.sh
> index d4c8005ce9b9..02d9ef27c8e7 100755
> --- a/tools/perf/tests/shell/pipe_test.sh
> +++ b/tools/perf/tests/shell/pipe_test.sh
> @@ -12,7 +12,7 @@ skip_test_missing_symbol ${sym}
>
> data=$(mktemp /tmp/perf.data.XXXXXX)
> data2=$(mktemp /tmp/perf.data2.XXXXXX)
> -prog="perf test -w noploop"
> +prog="perf test -w noploop 3"
> err=0
>
> set -e
> --
> 2.47.0
>
next prev parent reply other threads:[~2024-10-17 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 7:47 [PATCH] perf test: Fix perf test case 84 on s390 Thomas Richter
2024-10-17 20:28 ` Namhyung Kim [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-18 8:16 Thomas Richter
2024-10-18 16:11 ` Ian Rogers
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=ZxFzb7LEu9n9piVG@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=sumanthk@linux.ibm.com \
--cc=tmricht@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.