From: Jiri Olsa <jolsa@redhat.com>
To: Claire Jensen <cjense@google.com>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
namhyung@kernel.org, yao.jin@linux.intel.com, song@kernel.org,
andi@firstfloor.org, adrian.hunter@intel.com,
kan.liang@linux.intel.com, james.clark@arm.com,
alexander.antonov@linux.intel.com, changbin.du@intel.com,
liuqi115@huawei.com, irogers@google.com, eranian@google.com,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
clairej735@gmail.com
Subject: Re: [PATCH v2 1/1] Add field checking tests for perf stat JSON output.
Date: Tue, 31 Aug 2021 21:46:10 +0200 [thread overview]
Message-ID: <YS6HAvjCxq4kDk5z@krava> (raw)
In-Reply-To: <20210813220936.2105426-1-cjense@google.com>
On Fri, Aug 13, 2021 at 10:09:37PM +0000, Claire Jensen wrote:
> Counts number of fields to make sure expected fields are present.
>
> Signed-off-by: Claire Jensen <cjense@google.com>
> ---
> .../tests/shell/lib/perf_json_output_lint.py | 48 ++++++++
> tools/perf/tests/shell/stat+json_output.sh | 114 ++++++++++++++++++
> 2 files changed, 162 insertions(+)
> create mode 100644 tools/perf/tests/shell/lib/perf_json_output_lint.py
> create mode 100644 tools/perf/tests/shell/stat+json_output.sh
this one needs to have exec priv, right?
>
> diff --git a/tools/perf/tests/shell/lib/perf_json_output_lint.py b/tools/perf/tests/shell/lib/perf_json_output_lint.py
> new file mode 100644
> index 000000000000..45d9163e7423
> --- /dev/null
SNIP
> diff --git a/tools/perf/tests/shell/stat+json_output.sh b/tools/perf/tests/shell/stat+json_output.sh
> new file mode 100644
> index 000000000000..8a772badae45
> --- /dev/null
> +++ b/tools/perf/tests/shell/stat+json_output.sh
> @@ -0,0 +1,114 @@
> +#!/bin/bash
> +# perf stat JSON output linter
> +# SPDX-License-Identifier: GPL-2.0
> +# Checks various perf stat JSON output commands for the
> +# correct number of fields.
> +
> +set -e
> +set -x
> +
> +pythonchecker=$(dirname $0)/lib/perf_json_output_lint.py
> +file="/proc/sys/kernel/perf_event_paranoid"
> +paranoia=$(cat "$file" | grep -o -E '[0-9]+')
> +
> +check_no_args()
> +{
> + perf stat -j sleep 1 2>&1 | \
hum, is this based on some other change? I don't see -j option in perf stat
jirka
> + python $pythonchecker --no-args
> +}
> +
> +if [ $paranoia -gt 0 ];
> +then
> + echo check_all_cpus test skipped because of paranoia level.
> +else
> + check_all_cpus()
> + {
> + perf stat -j -a 2>&1 sleep 1 | \
> + python $pythonchecker --all-cpus
> + }
SNIP
next prev parent reply other threads:[~2021-08-31 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 22:09 [PATCH v2 1/1] Add field checking tests for perf stat JSON output Claire Jensen
2021-08-31 19:46 ` Jiri Olsa [this message]
2022-01-03 14:53 ` Arnaldo Carvalho de Melo
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=YS6HAvjCxq4kDk5z@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.antonov@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=changbin.du@intel.com \
--cc=cjense@google.com \
--cc=clairej735@gmail.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=liuqi115@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=song@kernel.org \
--cc=yao.jin@linux.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