public inbox for linux-perf-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Richter <tmricht@linux.ibm.com>
To: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
	linux-perf-users@vger.kernel.org, acme@kernel.org,
	namhyung@kernel.org, irogers@google.com, howardchu95@gmail.com
Cc: agordeev@linux.ibm.com, gor@linux.ibm.com,
	sumanthk@linux.ibm.com, hca@linux.ibm.com, japo@linux.ibm.com,
	Thomas Richter <tmricht@linux.ibm.com>
Subject: [PATCH] perf test: Run test 126 exclusive
Date: Wed,  8 Apr 2026 13:07:07 +0200	[thread overview]
Message-ID: <20260408110707.1455185-1-tmricht@linux.ibm.com> (raw)

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
 #

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 126 exclusive and it works.

Output after:
 # for i in $(seq 3); do perf test 126 128; done
 126: perf trace exit race                           : Ok
 128: mmap interface tests                           :
 128.1: Read samples using the mmap interface        : Ok
 128.2: User space counter reading of instructions   : Ok
 128.3: User space counter reading of cycles         : Ok
 128.4: User space counter disabling instructions    : Ok
 128.5: User space counter disabling cycles          : Ok
 126: perf trace exit race                           : Ok
 128: mmap interface tests                           :
 128.1: Read samples using the mmap interface        : Ok
 128.2: User space counter reading of instructions   : Ok
 128.3: User space counter reading of cycles         : Ok
 128.4: User space counter disabling instructions    : Ok
 128.5: User space counter disabling cycles          : Ok
 126: perf trace exit race                           : Ok
 128: mmap interface tests                           :
 128.1: Read samples using the mmap interface        : Ok
 128.2: User space counter reading of instructions   : Ok
 128.3: User space counter reading of cycles         : Ok
 128.4: User space counter disabling instructions    : Ok
 128.5: User space counter disabling cycles          : Ok
 #

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-08 11:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-08 11:07 Thomas Richter [this message]
2026-04-08 11:14 ` [PATCH] perf test: Run test 126 exclusive sashiko-bot

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=20260408110707.1455185-1-tmricht@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=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=namhyung@kernel.org \
    --cc=sumanthk@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