public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@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, acme@kernel.org,
	irogers@google.com, howardchu95@gmail.com,
	agordeev@linux.ibm.com, gor@linux.ibm.com,
	sumanthk@linux.ibm.com, hca@linux.ibm.com, japo@linux.ibm.com
Subject: Re: [PATCH v2] perf test: Run test 126 exclusive
Date: Wed, 8 Apr 2026 19:31:20 -0700	[thread overview]
Message-ID: <adcPeB5qc0M0K8Fw@google.com> (raw)
In-Reply-To: <20260408113143.1645091-1-tmricht@linux.ibm.com>

On Wed, Apr 08, 2026 at 01:31:43PM +0200, Thomas Richter wrote:
> V1 --> V2 Fixed commit message
> 
> Running both tests cases 126 128 together causes the first test case
> 126 to fail:
>  # for i in $(seq 3); do ./perf test 126 128; done
>  126: perf trace BTF general tests    : FAILED!
>  128: perf trace record and replay    : Ok
>  126: perf trace BTF general tests    : FAILED!
>  128: perf trace record and replay    : Ok
>  126: perf trace BTF general tests    : FAILED!
>  128: perf trace record and replay    : Ok
>  #

The test numbers can be different on other platforms, let's use the test
names like below.

> 
> Test case 126 fails because test case 128 runs concurrently as can
> be observed using a ps -ef | grep perf output list on a different
> window. Both do a perf trace command concurrently.
> Make test case 'perf trace BTF general tests' exclusive.
> 
> Output after:
>  # for i in $(seq 3); do ./perf test 'perf trace BTF general tests' \
> 	'perf trace record and replay'; done
>  127: perf trace BTF general tests                   : Ok
>  155: perf trace record and replay                   : Ok
>  127: perf trace BTF general tests                   : Ok
>  155: perf trace record and replay                   : Ok
>  127: perf trace BTF general tests                   : Ok
>  155: perf trace record and replay                   : Ok
>  #

I believe I have a fix for this problem but it's blocked by a BPF
verifier issue.  I need to find time to work on it again..

https://lore.kernel.org/linux-perf-users/20250814071754.193265-1-namhyung@kernel.org/

Until then, I think it's ok to have this.

Thanks,
Namhyung

> 
> Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
> Cc: Howard Chu <howardchu95@gmail.com>
> ---
>  tools/perf/tests/shell/trace_btf_general.sh | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/perf/tests/shell/trace_btf_general.sh b/tools/perf/tests/shell/trace_btf_general.sh
> index ef2da806be6b..7a94a5743924 100755
> --- a/tools/perf/tests/shell/trace_btf_general.sh
> +++ b/tools/perf/tests/shell/trace_btf_general.sh
> @@ -1,5 +1,5 @@
>  #!/bin/bash
> -# perf trace BTF general tests
> +# perf trace BTF general tests (exclusive)
>  # SPDX-License-Identifier: GPL-2.0
>  
>  err=0
> -- 
> 2.53.0
> 

  reply	other threads:[~2026-04-09  2:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-08 11:31 [PATCH v2] perf test: Run test 126 exclusive Thomas Richter
2026-04-09  2:31 ` Namhyung Kim [this message]
2026-04-09  2:44   ` Howard Chu
2026-04-09 16:46 ` Namhyung Kim

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=adcPeB5qc0M0K8Fw@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=howardchu95@gmail.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=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