[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZYMk2zh7jTzMiz8K@kernel.org>
Date: Wed, 20 Dec 2023 14:31:07 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Ruidong Tian <tianruidong@...ux.alibaba.com>
Cc: linux-kernel@...r.kernel.org, james.clark@....com,
coresight@...ts.linaro.org, suzuki.poulose@....com,
mike.leach@...aro.org, alexander.shishkin@...ux.intel.com,
linux-arm-kernel@...ts.infradead.org, adrian.hunter@...el.com,
linux-perf-users@...r.kernel.org, leo.yan@...aro.org,
al.grant@....com, mathieu.poirier@...aro.org, tor@...com,
acme@...hat.com
Subject: Re: [PATCH 0/3] perf scripts python: arm-cs-trace-disasm.py:
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
Powered by blists - more mailing lists