From: Ian Rogers <irogers@google.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Thomas Richter <tmricht@linux.ibm.com>,
Sumanth Korikkar <sumanthk@linux.ibm.com>,
Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] Write json and csv test output to test files
Date: Fri, 7 Apr 2023 22:44:53 -0700 [thread overview]
Message-ID: <20230408054456.3001367-1-irogers@google.com> (raw)
Avoid problems where debug/warning messages would break output
formatting.
v2. move the XXX with mktemp to the end of the template as required.
Ian Rogers (3):
perf test: Write CSV output to a file
perf stat: Don't write "started on" for json output
perf test: Write Json output to a file
tools/perf/builtin-stat.c | 6 +-
.../tests/shell/lib/perf_json_output_lint.py | 3 +-
tools/perf/tests/shell/stat+csv_output.sh | 58 ++++++++++++++-----
tools/perf/tests/shell/stat+json_output.sh | 48 +++++++++++----
4 files changed, 84 insertions(+), 31 deletions(-)
--
2.40.0.577.gac1e443424-goog
next reply other threads:[~2023-04-08 5:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 5:44 Ian Rogers [this message]
2023-04-08 5:44 ` [PATCH v2 1/3] perf test: Write CSV output to a file Ian Rogers
2023-04-08 5:44 ` [PATCH v2 2/3] perf stat: Don't write "started on" for json output Ian Rogers
2023-04-08 5:44 ` [PATCH v2 3/3] perf test: Write Json output to a file Ian Rogers
2023-04-10 22:16 ` [PATCH v2 0/3] Write json and csv test output to test files 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=20230408054456.3001367-1-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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 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).