From: Namhyung Kim <namhyung@kernel.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v8 4/4] Add a test case for perf script -F +metric
Date: Mon, 5 Aug 2024 12:25:49 -0700 [thread overview]
Message-ID: <ZrEnPYNK-59eGjoy@google.com> (raw)
In-Reply-To: <20240801212844.677895-4-ak@linux.intel.com>
On Thu, Aug 01, 2024 at 02:28:44PM -0700, Andi Kleen wrote:
> Just a simple test
Can you please briefly describe what the test does? Ideally with an
example output with 'perf test -vv'.
Thanks,
Namhyung
>
> Signed-off-by: Andi Kleen <ak@linux.intel.com>
>
> ----
>
> v2: Avoid bashisms. Use noploop
> v3: Avoid false positive in shellcheck
> v4: Use :S in the test (Ian, Namhyung)
> ---
> tools/perf/tests/shell/script.sh | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/tools/perf/tests/shell/script.sh b/tools/perf/tests/shell/script.sh
> index c1a603653662..e69c3548583a 100755
> --- a/tools/perf/tests/shell/script.sh
> +++ b/tools/perf/tests/shell/script.sh
> @@ -7,6 +7,7 @@ set -e
> temp_dir=$(mktemp -d /tmp/perf-test-script.XXXXXXXXXX)
>
> perfdatafile="${temp_dir}/perf.data"
> +scriptoutput="${temp_dir}/script"
> db_test="${temp_dir}/db_test.py"
>
> err=0
> @@ -88,8 +89,21 @@ test_parallel_perf()
> echo "parallel-perf test [Success]"
> }
>
> +test_metric()
> +{
> + echo "script metric test"
> + if ! perf list | grep -q cycles ; then return ; fi
> + if ! perf list | grep -q instructions ; then return ; fi
> + perf record -e '{cycles,instructions}:S' -o "${perfdatafile}" perf test -w noploop
> + perf script -i "${perfdatafile}" -F +metric > $scriptoutput
> + test "`grep -c metric $scriptoutput`" -gt 5
> + grep metric $scriptoutput | head
> + echo "script metric test [Success]"
> +}
> +
> test_db
> test_parallel_perf
> +test_metric
>
> cleanup
>
> --
> 2.45.2
>
next prev parent reply other threads:[~2024-08-05 19:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 21:28 [PATCH v8 1/4] Create source symlink in perf object dir Andi Kleen
2024-08-01 21:28 ` [PATCH v8 2/4] perf test: Support external tests for separate objdir Andi Kleen
2024-08-05 19:02 ` Namhyung Kim
2024-08-01 21:28 ` [PATCH v8 3/4] perf script: Fix perf script -F +metric Andi Kleen
2024-08-05 19:23 ` Namhyung Kim
2024-08-01 21:28 ` [PATCH v8 4/4] Add a test case for " Andi Kleen
2024-08-05 19:25 ` Namhyung Kim [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-07 3:30 [PATCH v8 1/4] Create source symlink in perf object dir Andi Kleen
2024-08-07 3:30 ` [PATCH v8 4/4] Add a test case for perf script -F +metric Andi Kleen
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=ZrEnPYNK-59eGjoy@google.com \
--to=namhyung@kernel.org \
--cc=ak@linux.intel.com \
--cc=linux-perf-users@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).