From: Namhyung Kim <namhyung@gmail.com>
To: weilin.wang@intel.com
Cc: namhyung@google.com, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Perry Taylor <perry.taylor@intel.com>,
Samantha Alt <samantha.alt@intel.com>,
Caleb Biggers <caleb.biggers@intel.com>
Subject: Re: [RFC PATCH v10 8/8] perf test: Add test for Intel TPEBS counting mode
Date: Sun, 2 Jun 2024 16:20:31 -0700 [thread overview]
Message-ID: <20240602232041.1730256-1-namhyung@google.com> (raw)
In-Reply-To: <20240529064327.4080674-9-weilin.wang@intel.com>
From: namhyung@google.com
On Wed, 29 May 2024 02:43:24 -0400 weilin.wang@intel.com wrote:
> From: Weilin Wang <weilin.wang@intel.com>
>
> Intel TPEBS sampling mode is supported through perf record. The counting mode
> code uses perf record to capture retire_latency value and use it in metric
> calculation. This test checks the counting mode code.
>
> Signed-off-by: Weilin Wang <weilin.wang@intel.com>
> ---
> .../perf/tests/shell/test_stat_intel_tpebs.sh | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
> create mode 100755 tools/perf/tests/shell/test_stat_intel_tpebs.sh
>
> diff --git a/tools/perf/tests/shell/test_stat_intel_tpebs.sh b/tools/perf/tests/shell/test_stat_intel_tpebs.sh
> new file mode 100755
> index 000000000000..43f75055fee4
> --- /dev/null
> +++ b/tools/perf/tests/shell/test_stat_intel_tpebs.sh
> @@ -0,0 +1,19 @@
> +#!/bin/bash
> +# test Intel TPEBS counting mode
> +# SPDX-License-Identifier: GPL-2.0
> +
> +set e
> +err=0
> +
> +# Use this event for testing because it should exist in all platforms
> +e=cache-misses:R
> +
> +# Without this cmd option, default value or zero is returned
> +echo "Testing without --enable-tpebs-recording"
> +result=$(perf stat -e "$e" true 2>&1)
> +[[ "$result" =~ "$e" ]] || exit 1
> +
> +# In platforms that do not support TPEBS, it should execute without error.
> +echo "Testing with --enable-tpebs-recording"
> +result=$(perf stat -e "$e" --enable-tpebs-recording -a sleep 0.01 2>&1)
> +[[ "$result" =~ "perf record" && "$result" =~ "$e" ]] || exit 1
I got these build errors:
Thanks,
Namhyung
---
TEST tests/shell/test_stat_intel_tpebs.sh.shellcheck_log
In tests/shell/test_stat_intel_tpebs.sh line 6:
err=0
^-^ SC2034 (warning): err appears unused. Verify use (or export if used externally).
In tests/shell/test_stat_intel_tpebs.sh line 14:
[[ "$result" =~ "$e" ]] || exit 1
^--^ SC2076 (warning): Remove quotes from right-hand side of =~ to match as a regex rather than literally.
In tests/shell/test_stat_intel_tpebs.sh line 19:
[[ "$result" =~ "perf record" && "$result" =~ "$e" ]] || exit 1
^--^ SC2076 (warning): Remove quotes from right-hand side of =~ to match as a regex rather than literally.
For more information:
https://www.shellcheck.net/wiki/SC2034 -- err appears unused. Verify use (o...
https://www.shellcheck.net/wiki/SC2076 -- Remove quotes from right-hand sid...
make[4]: *** [tests/Build:91: tests/shell/test_stat_intel_tpebs.sh.shellcheck_log] Error 1
next prev parent reply other threads:[~2024-06-02 23:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 6:43 [RFC PATCH v10 0/8] TPEBS counting mode support weilin.wang
2024-05-29 6:43 ` [RFC PATCH v10 1/8] perf parse-events: Add a retirement latency modifier weilin.wang
2024-05-29 6:43 ` [RFC PATCH v10 2/8] perf data: Allow to use given fd in data->file.fd weilin.wang
2024-05-29 6:43 ` [RFC PATCH v10 3/8] perf stat: Fork and launch perf record when perf stat needs to get retire latency value for a metric weilin.wang
2024-05-31 6:40 ` Namhyung Kim
2024-05-31 6:46 ` Wang, Weilin
2024-05-31 21:39 ` Namhyung Kim
2024-05-31 23:04 ` Wang, Weilin
2024-06-04 20:00 ` Wang, Weilin
2024-06-04 22:32 ` Namhyung Kim
2024-06-04 22:41 ` Ian Rogers
2024-06-04 23:56 ` Ian Rogers
2024-05-29 6:43 ` [RFC PATCH v10 4/8] perf stat: Plugin retire_lat value from sampled data to evsel weilin.wang
2024-05-29 6:43 ` [RFC PATCH v10 5/8] perf vendor events intel: Add MTL metric json files weilin.wang
2024-05-29 6:43 ` [RFC PATCH v10 6/8] perf stat: Add command line option for enabling tpebs recording weilin.wang
2024-05-29 6:43 ` [RFC PATCH v10 7/8] perf Document: Add TPEBS to Documents weilin.wang
2024-05-29 6:43 ` [RFC PATCH v10 8/8] perf test: Add test for Intel TPEBS counting mode weilin.wang
2024-06-02 23:20 ` Namhyung Kim [this message]
2024-06-03 17:00 ` Wang, Weilin
2024-05-31 6:37 ` [RFC PATCH v10 0/8] TPEBS counting mode support Namhyung Kim
2024-05-31 7:00 ` Wang, Weilin
2024-05-31 21:30 ` Namhyung Kim
2024-05-31 23:03 ` Wang, Weilin
2024-06-02 21:18 ` Namhyung Kim
2024-06-03 17:00 ` Wang, Weilin
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=20240602232041.1730256-1-namhyung@google.com \
--to=namhyung@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=caleb.biggers@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@google.com \
--cc=namhyung@kernel.org \
--cc=perry.taylor@intel.com \
--cc=peterz@infradead.org \
--cc=samantha.alt@intel.com \
--cc=weilin.wang@intel.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
all inboxes | Powered by JetHome®