From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ruidong Tian <tianruidong@linux.alibaba.com>
Cc: linux-kernel@vger.kernel.org, james.clark@arm.com,
coresight@lists.linaro.org, suzuki.poulose@arm.com,
mike.leach@linaro.org, alexander.shishkin@linux.intel.com,
linux-arm-kernel@lists.infradead.org, adrian.hunter@intel.com,
linux-perf-users@vger.kernel.org, leo.yan@linaro.org,
al.grant@arm.com, mathieu.poirier@linaro.org, tor@ti.com,
acme@redhat.com
Subject: Re: [PATCH 0/3] perf scripts python: arm-cs-trace-disasm.py:
Date: Wed, 20 Dec 2023 14:31:07 -0300 [thread overview]
Message-ID: <ZYMk2zh7jTzMiz8K@kernel.org> (raw)
In-Reply-To: <20231214123304.34087-1-tianruidong@linux.alibaba.com>
Em Thu, Dec 14, 2023 at 08:33:01PM +0800, Ruidong Tian escreveu:
> Now the instruction flow disasmed by arm-cs-trace-disasm.py is
> ambiguous and uncorrect, fix them in one patch set. Please refer to
> each patch for details.
>
> Ruidong Tian (3):
> perf scripts python: arm-cs-trace-disasm.py: print dso base address
> perf scripts python: arm-cs-trace-disasm.py: set start vm addr of
> exectable file to 0
> perf scripts python: arm-cs-trace-disasm.py: do not ignore disam first
> sample
Picked patches 2 and 3, waiting for further discussion about the other
one.
- Arnaldo
next prev parent reply other threads:[~2023-12-20 17:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 12:33 [PATCH 0/3] perf scripts python: arm-cs-trace-disasm.py: Ruidong Tian
2023-12-14 12:33 ` [PATCH 1/3] perf scripts python: arm-cs-trace-disasm.py: print dso base address Ruidong Tian
2023-12-20 10:44 ` James Clark
2023-12-22 7:29 ` Ruidong Tian
2023-12-24 8:33 ` Leo Yan
2023-12-14 12:33 ` [PATCH 2/3] perf scripts python: arm-cs-trace-disasm.py: set start vm addr of exectable file to 0 Ruidong Tian
2023-12-20 12:06 ` James Clark
2023-12-14 12:33 ` [PATCH 3/3] perf scripts python: arm-cs-trace-disasm.py: do not ignore disam first sample Ruidong Tian
2023-12-18 20:28 ` Arnaldo Carvalho de Melo
2023-12-20 11:15 ` James Clark
2023-12-20 17:31 ` Arnaldo Carvalho de Melo [this message]
2024-01-10 2:56 ` [PATCH v2 0/1] perf scripts python: arm-cs-trace-disasm.py: print correct disasm info Ruidong Tian
2024-01-10 2:56 ` [PATCH v2 1/1] perf scripts python: arm-cs-trace-disasm.py: add option to print virtual address Ruidong Tian
2024-01-10 12:55 ` Leo Yan
2024-01-10 13:48 ` Ruidong Tian
2024-01-16 2:08 ` [PATCH v3 0/1] perf scripts python: arm-cs-trace-disasm.py: print correct disasm info Ruidong Tian
2024-01-16 2:08 ` [PATCH v3 1/1] perf scripts python: arm-cs-trace-disasm.py: add option to print virtual address Ruidong Tian
2024-01-17 10:16 ` James Clark
2024-01-16 2:08 ` [PATCH v3 2/3] perf scripts python: arm-cs-trace-disasm.py: set start vm addr of exectable file to 0 Ruidong Tian
2024-01-17 10:12 ` James Clark
2024-01-16 2:08 ` Ruidong Tian
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=ZYMk2zh7jTzMiz8K@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=al.grant@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@arm.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@arm.com \
--cc=tianruidong@linux.alibaba.com \
--cc=tor@ti.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).