From: Anup Sharma <anupnewsmail@gmail.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>,
Anup Sharma <anupnewsmail@gmail.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Add support for firefox gecko converter test and commands
Date: Thu, 20 Jul 2023 19:52:21 +0530 [thread overview]
Message-ID: <cover.1689862609.git.anupnewsmail@gmail.com> (raw)
This patchset adds support for firefox gecko converter test and commands.
The firefox gecko converter is a python script which converts the
perf.data file into firefox gecko profile format. The script is
available at tools/perf/scripts/python/firefox-gecko-converter.py
Anup Sharma (2):
perf scripts python: Add command execution for converter
perf test: Add support for testing firefox-gecko-converter script
.../python/bin/firefox-gecko-converter-record | 2 +
.../python/bin/firefox-gecko-converter-report | 3 +
.../shell/test_firefox-gecko-converter.sh | 190 ++++++++++++++++++
3 files changed, 195 insertions(+)
create mode 100755 tools/perf/scripts/python/bin/firefox-gecko-converter-record
create mode 100755 tools/perf/scripts/python/bin/firefox-gecko-converter-report
create mode 100755 tools/perf/tests/shell/test_firefox-gecko-converter.sh
--
2.34.1
next reply other threads:[~2023-07-20 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 14:22 Anup Sharma [this message]
2023-07-20 14:23 ` [PATCH 1/2] perf scripts python: Add command execution for firefox gecko converter script Anup Sharma
2023-07-20 14:24 ` [PATCH 2/2] perf test: Add support for testing " Anup Sharma
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=cover.1689862609.git.anupnewsmail@gmail.com \
--to=anupnewsmail@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.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 \
/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.