From: Changbin Du <changbin.du@huawei.com>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Changbin Du <changbin.du@huawei.com>,
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>, <linux-kernel@vger.kernel.org>,
<linux-perf-users@vger.kernel.org>,
Andi Kleen <ak@linux.intel.com>,
Thomas Richter <tmricht@linux.ibm.com>, <changbin.du@gmail.com>
Subject: Re: [PATCH v5 3/5] perf: script: add field 'disasm' to display mnemonic instructions
Date: Tue, 6 Feb 2024 10:00:56 +0800 [thread overview]
Message-ID: <20240206020056.tpy2c6ycok4podjd@M910t> (raw)
In-Reply-To: <1ff39c81-f207-480a-8169-85b273631594@intel.com>
On Mon, Feb 05, 2024 at 03:10:58PM +0200, Adrian Hunter wrote:
> On 5/02/24 14:19, Changbin Du wrote:
> > On Mon, Feb 05, 2024 at 11:23:21AM +0200, Adrian Hunter wrote:
> >>> struct perf_script {
> >>> @@ -190,6 +191,7 @@ struct output_option {
> >>> {.str = "bpf-output", .field = PERF_OUTPUT_BPF_OUTPUT},
> >>> {.str = "callindent", .field = PERF_OUTPUT_CALLINDENT},
> >>> {.str = "insn", .field = PERF_OUTPUT_INSN},
> >>> + {.str = "disasm", .field = PERF_OUTPUT_DISASM},
> >>> {.str = "insnlen", .field = PERF_OUTPUT_INSNLEN},
> >>> {.str = "brstackinsn", .field = PERF_OUTPUT_BRSTACKINSN},
> >>> {.str = "brstackoff", .field = PERF_OUTPUT_BRSTACKOFF},
> >>> @@ -1515,6 +1517,10 @@ static int perf_sample__fprintf_insn(struct perf_sample *sample,
> >>> printed += fprintf(fp, " insn: ");
> >>> printed += sample__fprintf_insn_raw(sample, fp);
> >>> }
> >>> + if (PRINT_FIELD(DISASM) && sample->insn_len) {
> >>> + printed += fprintf(fp, "\t\t");
> >>
> >> This is good, except if both 'insn' and 'disasm' are used together.
> >> It either:
> >> a) without libcapstone, prints insn bytes twice
> >>
> >> Probably simpler to make 'disasm' without libcapstone
> >> a fatal error explaining that perf needs to be built
> >> with libcapstone support for 'disasm' to work.
> >>
> > Instead of fatal error, I print a warning message for this. Because
> > perf_sample__fprintf_insn() cannot return negtive error number.
>
> It could be validated in advance, perhaps in parse_output_fields().
>
I did as below:
--- a/tools/perf/builtin-script.c
+++ b/tools/perf/builtin-script.c
@@ -3112,6 +3112,13 @@ static int parse_output_fields(const struct option *opt __maybe_unused,
rc = -EINVAL;
goto out;
}
+#ifndef HAVE_LIBCAPSTONE_SUPPORT
+ if (change != REMOVE && strcmp(tok, "disasm") == 0) {
+ fprintf(stderr, "Field \"disasm\" requires perf to be built with libcapstone support.\n");
+ rc = -EINVAL;
+ goto out;
+ }
+#endif
Then,
$ sudo perf script -F +disasm
Field "disasm" requires perf to be built with libcapstone support.
Usage: perf script [<options>]
...
> >
> >> b) with libcapstone, disassembly does not line up nicely
> >>
> >
> >
>
--
Cheers,
Changbin Du
next prev parent reply other threads:[~2024-02-06 2:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 11:20 [PATCH v5 0/5] perf: script: Intro capstone disasm engine to show instruction trace Changbin Du
2024-01-22 11:20 ` [PATCH v5 1/5] perf: build: introduce the libcapstone Changbin Du
2024-02-05 9:21 ` Adrian Hunter
2024-02-05 11:51 ` Changbin Du
2024-01-22 11:20 ` [PATCH v5 2/5] perf: util: use capstone disasm engine to show assembly instructions Changbin Du
2024-02-05 9:22 ` Adrian Hunter
2024-02-05 11:36 ` Changbin Du
2024-01-22 11:20 ` [PATCH v5 3/5] perf: script: add field 'disasm' to display mnemonic instructions Changbin Du
2024-02-05 9:23 ` Adrian Hunter
2024-02-05 11:41 ` Changbin Du
2024-02-05 12:19 ` Changbin Du
2024-02-05 13:10 ` Adrian Hunter
2024-02-06 2:00 ` Changbin Du [this message]
2024-01-22 11:20 ` [PATCH v5 4/5] perf: script: add raw|disasm arguments to --insn-trace option Changbin Du
2024-01-22 11:20 ` [PATCH v5 5/5] perf: script: prefer capstone to XED Changbin Du
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=20240206020056.tpy2c6ycok4podjd@M910t \
--to=changbin.du@huawei.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=changbin.du@gmail.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 \
--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).