From: Leo Yan <leo.yan@arm.com>
To: James Clark <james.clark@linaro.org>,
linux-perf-users@vger.kernel.org,
gankulkarni@os.amperecomputing.com, coresight@lists.linaro.org,
scclevenger@os.amperecomputing.com
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
"Liang, Kan" <kan.liang@linux.intel.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Mike Leach <mike.leach@linaro.org>,
John Garry <john.g.garry@oracle.com>,
Will Deacon <will@kernel.org>, Leo Yan <leo.yan@linux.dev>,
Ben Gainey <ben.gainey@arm.com>,
Ruidong Tian <tianruidong@linux.alibaba.com>,
Benjamin Gray <bgray@linux.ibm.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 6/7] perf scripts python cs-etm: Add start and stop arguments
Date: Fri, 13 Sep 2024 14:20:43 +0100 [thread overview]
Message-ID: <11bca9b1-7eb1-4a13-8f05-9ba5b9c46d24@arm.com> (raw)
In-Reply-To: <20240912151143.1264483-7-james.clark@linaro.org>
On 9/12/24 16:11, James Clark wrote:>
> Make it possible to only disassemble a range of timestamps or sample
> indexes. This will be used by the test to limit the runtime, but it's
> also useful for users.
>
> Signed-off-by: James Clark <james.clark@linaro.org>
> ---
> .../scripts/python/arm-cs-trace-disasm.py | 22 +++++++++++++++++--
> 1 file changed, 20 insertions(+), 2 deletions(-)
>
> diff --git a/tools/perf/scripts/python/arm-cs-trace-disasm.py b/tools/perf/scripts/python/arm-cs-trace-disasm.py
> index 02e957d037ea..a097995d8e7b 100755
> --- a/tools/perf/scripts/python/arm-cs-trace-disasm.py
> +++ b/tools/perf/scripts/python/arm-cs-trace-disasm.py
> @@ -55,6 +55,11 @@ args.add_argument("-k", "--vmlinux",
> args.add_argument("-d", "--objdump", nargs="?", const=default_objdump(),
> help="Show disassembly. Can also be used to change the objdump path"),
> args.add_argument("-v", "--verbose", action="store_true", help="Enable debugging log")
> +args.add_argument("--start-time", type=int, help="Time of sample to start from")
> +args.add_argument("--stop-time", type=int, help="Time of sample to stop at")
> +args.add_argument("--start-sample", type=int, help="Index of sample to start from")
> +args.add_argument("--stop-sample", type=int, help="Index of sample to stop at")
> +
It is good to validate the ranges for time and sample indexes, in case
the user passes unexpected values and can directly report the error.
BTW, I think it is good to clarify the time is based on monotonic clock
but not wall-clock time.
With above changes, LGTM:
Reviewed-by: Leo Yan <leo.yan@arm.com>
> options = args.parse_args()
>
> # Initialize global dicts and regular expression
> @@ -63,6 +68,7 @@ cpu_data = dict()
> disasm_re = re.compile(r"^\s*([0-9a-fA-F]+):")
> disasm_func_re = re.compile(r"^\s*([0-9a-fA-F]+)\s.*:")
> cache_size = 64*1024
> +sample_idx = -1
>
> glb_source_file_name = None
> glb_line_number = None
> @@ -151,10 +157,10 @@ def print_disam(dso_fname, dso_start, start_addr, stop_addr):
>
> def print_sample(sample):
> print("Sample = { cpu: %04d addr: 0x%016x phys_addr: 0x%016x ip: 0x%016x " \
> - "pid: %d tid: %d period: %d time: %d }" % \
> + "pid: %d tid: %d period: %d time: %d index: %d}" % \
> (sample['cpu'], sample['addr'], sample['phys_addr'], \
> sample['ip'], sample['pid'], sample['tid'], \
> - sample['period'], sample['time']))
> + sample['period'], sample['time'], sample_idx))
>
> def trace_begin():
> print('ARM CoreSight Trace Data Assembler Dump')
> @@ -216,6 +222,7 @@ def print_srccode(comm, param_dict, sample, symbol, dso):
> def process_event(param_dict):
> global cache_size
> global options
> + global sample_idx
>
> sample = param_dict["sample"]
> comm = param_dict["comm"]
> @@ -231,6 +238,17 @@ def process_event(param_dict):
> ip = sample["ip"]
> addr = sample["addr"]
>
> + sample_idx += 1
> +
> + if (options.start_time and sample["time"] < options.start_time):
> + return
> + if (options.stop_time and sample["time"] > options.stop_time):
> + exit(0)
> + if (options.start_sample and sample_idx < options.start_sample):
> + return
> + if (options.stop_sample and sample_idx > options.stop_sample):
> + exit(0)
> +
> if (options.verbose == True):
> print("Event type: %s" % name)
> print_sample(sample)
> --
> 2.34.1
>
next prev parent reply other threads:[~2024-09-13 13:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 15:11 [PATCH v2 0/7] perf: cs-etm: Coresight decode and disassembly improvements James Clark
2024-09-12 15:11 ` [PATCH v2 1/7] perf cs-etm: Don't flush when packet_queue fills up James Clark
2024-09-13 11:17 ` Leo Yan
2024-09-12 15:11 ` [PATCH v2 2/7] perf cs-etm: Use new OpenCSD consistency checks James Clark
2024-09-13 11:54 ` Leo Yan
2024-09-13 12:09 ` James Clark
2024-09-13 13:03 ` Leo Yan
2024-09-12 15:11 ` [PATCH v2 3/7] perf scripting python: Add function to get a config value James Clark
2024-09-13 13:40 ` Leo Yan
2024-09-12 15:11 ` [PATCH v2 4/7] perf scripts python cs-etm: Update to use argparse James Clark
2024-09-13 12:44 ` Leo Yan
2024-09-12 15:11 ` [PATCH v2 5/7] perf scripts python cs-etm: Improve arguments James Clark
2024-09-13 13:01 ` Leo Yan
2024-09-12 15:11 ` [PATCH v2 6/7] perf scripts python cs-etm: Add start and stop arguments James Clark
2024-09-13 13:20 ` Leo Yan [this message]
2024-09-16 10:41 ` James Clark
2024-09-12 15:11 ` [PATCH v2 7/7] perf test: cs-etm: Test Coresight disassembly script James Clark
2024-09-13 13:35 ` Leo Yan
2024-09-16 13:25 ` James Clark
2024-09-12 19:23 ` [PATCH v2 0/7] perf: cs-etm: Coresight decode and disassembly improvements Arnaldo Carvalho de Melo
2024-09-17 8:15 ` James Clark
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=11bca9b1-7eb1-4a13-8f05-9ba5b9c46d24@arm.com \
--to=leo.yan@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ben.gainey@arm.com \
--cc=bgray@linux.ibm.com \
--cc=coresight@lists.linaro.org \
--cc=gankulkarni@os.amperecomputing.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=leo.yan@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=scclevenger@os.amperecomputing.com \
--cc=suzuki.poulose@arm.com \
--cc=tianruidong@linux.alibaba.com \
--cc=will@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).