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,
ctshao@google.com, irogers@google.com, agordeev@linux.ibm.com,
gor@linux.ibm.com, sumanthk@linux.ibm.com, hca@linux.ibm.com
Subject: Re: [PING PATCH v3] perf test: Allow tolerance for leader sampling test
Date: Wed, 30 Apr 2025 09:56:54 -0300 [thread overview]
Message-ID: <aBIeFio2nkbzFj0b@x1> (raw)
In-Reply-To: <20250422110643.2900090-1-tmricht@linux.ibm.com>
On Tue, Apr 22, 2025 at 01:06:43PM +0200, Thomas Richter wrote:
> V3: Added check for missing samples as suggested by Chun-Tse.
> V2: Changed bc invocation to return 0 on success and 1 on error.
> There is a known issue that the leader sampling is inconsistent, since
> throttle only affect leader, not the slave. The detail is in [1]. To
> maintain test coverage, this patch sets a tolerance rate of 80% to
> accommodate the throttled samples and prevent test failures due to
> throttling.
> [1] lore.kernel.org/20250328182752.769662-1-ctshao@google.com
> Signed-off-by: Chun-Tse Shao <ctshao@google.com>
> Suggested-by: Ian Rogers <irogers@google.com>
> Suggested-by: Thomas Richter <tmricht@linux.ibm.com>
> Tested-by: Thomas Richter <tmricht@linux.ibm.com>
> Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
This doesn't apply to perf-tools-next:
⬢ [acme@toolbx perf-tools-next]$ git am ./v3_20250422_tmricht_perf_test_allow_tolerance_for_leader_sampling_test.mbx
Applying: perf test: Allow tolerance for leader sampling test
error: patch failed: tools/perf/tests/shell/record.sh:238
error: tools/perf/tests/shell/record.sh: patch does not apply
Patch failed at 0001 perf test: Allow tolerance for leader sampling test
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
⬢ [acme@toolbx perf-tools-next]$
Are you proposing this for perf-tools, i.e. for this release cycles?
Namhyung, what do you think?
I think it is not applying in perf-tools-next due to this patch that
isn't in perf-tools:
⬢ [acme@toolbx perf-tools-next]$ git log --oneline -5 perf-tools-next/perf-tools-next tools/perf/tests/shell/record.sh
be8aefad33760dd8 perf tests record: Cleanup improvements <<<<<<<<<<<<<<<<<<<<<<<<<<<<
90d97674d4ad0166 perf test: Use cycles event in perf record test for leader_sampling
859199431d768091 perf test: Fix perf record test for precise_max
180fd0c1eac7cd8c perf tests: Make leader sampling test work without branch event
2532be3d219d8819 perf test: Tag parallel failing shell tests with "(exclusive)"
⬢ [acme@toolbx perf-tools-next]$
⬢ [acme@toolbx perf-tools-next]$ git log --oneline -5 perf-tools/perf-tools tools/perf/tests/shell/record.sh
90d97674d4ad0166 perf test: Use cycles event in perf record test for leader_sampling
859199431d768091 perf test: Fix perf record test for precise_max
180fd0c1eac7cd8c perf tests: Make leader sampling test work without branch event
2532be3d219d8819 perf test: Tag parallel failing shell tests with "(exclusive)"
36fae9f93e5f00eb perf test: Add precise_max subtest to the perf record shell test
⬢ [acme@toolbx perf-tools-next]$
- Arnaldo
next prev parent reply other threads:[~2025-04-30 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 11:06 [PING PATCH v3] perf test: Allow tolerance for leader sampling test Thomas Richter
2025-04-30 12:56 ` Arnaldo Carvalho de Melo [this message]
2025-04-30 14:00 ` Thomas Richter
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=aBIeFio2nkbzFj0b@x1 \
--to=acme@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=ctshao@google.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=irogers@google.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 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.