[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aYotC6uRo4GP1AOr@x1>
Date: Mon, 9 Feb 2026 15:52:59 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Thomas Richter <tmricht@...ux.ibm.com>
Cc: linux-kernel@...r.kernel.org, linux-s390@...r.kernel.org,
linux-perf-users@...r.kernel.org, namhyung@...nel.org,
irogers@...gle.com, agordeev@...ux.ibm.com, gor@...ux.ibm.com,
sumanthk@...ux.ibm.com, hca@...ux.ibm.com, japo@...ux.ibm.com
Subject: Re: [PATCH linux-next] perf test: Fix test case
perftool-testsuite_report for s390
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
Powered by blists - more mailing lists