From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Thomas Richter <tmricht@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
linux-perf-users@vger.kernel.org, namhyung@kernel.org,
irogers@google.com, agordeev@linux.ibm.com, gor@linux.ibm.com,
sumanthk@linux.ibm.com, hca@linux.ibm.com, japo@linux.ibm.com
Subject: Re: [PATCH linux-next] perf test: Fix test case perftool-testsuite_report for s390
Date: Mon, 9 Feb 2026 15:52:59 -0300 [thread overview]
Message-ID: <aYotC6uRo4GP1AOr@x1> (raw)
In-Reply-To: <20260209153256.601599-1-tmricht@linux.ibm.com>
On Mon, Feb 09, 2026 at 04:32:56PM +0100, Thomas Richter wrote:
> Test case perftool-testsuite_report fails on s390 for some time
> now. Root cause is a time out which is too tight for large s390 machines.
> The time out value addr2line_timeout_ms is per default set to 1 second.
> This is the maximum time the function read_addr2line_record() waits
> for a reply from the forked off tool addr2line, which is started as a
> child in interactive mode. It reads stdin (an address in hexadecimal)
> and replies on stdout with function name, file name and line
> number. This might take more than one second.
<SNIP>
> +++ b/tools/perf/util/addr2line.c
> @@ -18,8 +18,8 @@
>
> #define MAX_INLINE_NEST 1024
>
> -/* If addr2line doesn't return data for 1 second then timeout. */
> -int addr2line_timeout_ms = 1 * 1000;
> +/* If addr2line doesn't return data for 5 seconds then timeout. */
> +int addr2line_timeout_ms = 5 * 1000;
> static int filename_split(char *filename, unsigned int *line_nr)
> {
Thanks, applied to perf-tools-next,
- Arnaldo
prev parent reply other threads:[~2026-02-09 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 15:32 [PATCH linux-next] perf test: Fix test case perftool-testsuite_report for s390 Thomas Richter
2026-02-09 18:52 ` Arnaldo Carvalho de Melo [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=aYotC6uRo4GP1AOr@x1 \
--to=acme@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=irogers@google.com \
--cc=japo@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=namhyung@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox