From: Namhyung Kim <namhyung@kernel.org>
To: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Changbin Du <changbin.du@huawei.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
linux-perf-users@vger.kernel.org, Ian Rogers <irogers@google.com>,
Thomas Richter <tmricht@linux.ibm.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Mark Rutland <mark.rutland@arm.com>,
Changbin Du <changbin.du@intel.com>
Subject: Re: [PATCH v8 0/5] perf: script: Intro capstone disasm engine to show instruction trace
Date: Thu, 22 Feb 2024 08:53:21 -0800 [thread overview]
Message-ID: <170862076568.3024784.8799548310369120740.b4-ty@kernel.org> (raw)
In-Reply-To: <20240217074046.4100789-1-changbin.du@huawei.com>
On Sat, 17 Feb 2024 15:40:41 +0800, Changbin Du wrote:
> This series introduces capstone disassembler engine to print instructions of
> Intel PT trace, which was printed via the XED tool.
>
> The advantages compared to XED tool:
> * Support arm, arm64, x86-32, x86_64, s390 (more could be supported),
> xed only for x86_64.
> * More friendly to read. Immediate address operands are shown as symbol+offs.
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
--
Namhyung Kim <namhyung@kernel.org>
prev parent reply other threads:[~2024-02-22 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 7:40 Changbin Du
2024-02-17 7:40 ` [PATCH v8 1/5] perf: build: introduce the libcapstone Changbin Du
2024-02-17 7:40 ` [PATCH v8 2/5] perf: util: use capstone disasm engine to show assembly instructions Changbin Du
2024-02-19 6:33 ` Adrian Hunter
2024-02-21 2:04 ` Namhyung Kim
2024-02-17 7:40 ` [PATCH v8 3/5] perf: script: add field 'disasm' to display mnemonic instructions Changbin Du
2024-02-17 7:40 ` [PATCH v8 4/5] perf: script: add raw|disasm arguments to --insn-trace option Changbin Du
2024-02-17 7:40 ` [PATCH v8 5/5] perf: script: prefer capstone to XED Changbin Du
2024-02-22 16:53 ` Namhyung Kim [this message]
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=170862076568.3024784.8799548310369120740.b4-ty@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=changbin.du@huawei.com \
--cc=changbin.du@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=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
all inboxes | Powered by JetHome®