On Thu, Nov 08, 2018 at 04:51:52PM +0800, leo@linaro.org wrote:
> Hi Jiri,
>
> On Wed, Nov 07, 2018 at 03:10:06PM +0100, Jiri Olsa wrote:
> > On Fri, Nov 02, 2018 at 10:55:16AM +0800, leo@linaro.org wrote:
> > > Hi all,
> > >
> > > Now I found that if use the command 'perf script' for Arm
Hi Jiri,
On Wed, Nov 07, 2018 at 03:10:06PM +0100, Jiri Olsa wrote:
> On Fri, Nov 02, 2018 at 10:55:16AM +0800, leo@linaro.org wrote:
> > Hi all,
> >
> > Now I found that if use the command 'perf script' for Arm CoreSight trace
> > data, it fails to parse kernel symbols if we don't specify ke
On Fri, Nov 02, 2018 at 10:55:16AM +0800, leo@linaro.org wrote:
> Hi all,
>
> Now I found that if use the command 'perf script' for Arm CoreSight trace
> data, it fails to parse kernel symbols if we don't specify kernel vmlinux
> file. So when we don't specify kernel symbol files then perf t
On Fri, Nov 02, 2018 at 10:55:16AM +0800, Leo Yan wrote:
> Hi all,
>
> Now I found that if use the command 'perf script' for Arm CoreSight trace
> data, it fails to parse kernel symbols if we don't specify kernel vmlinux
> file. So when we don't specify kernel symbol files then perf tool will
>
On Fri, Nov 02, 2018 at 02:12:28PM +, Al Grant wrote:
> > root@debian:~/coresight_test# perf buildid-list
> > 0242d9154c78df1d8fe1d0512c36a236d0861a18 [kernel.kallsyms]
> > b8c89e8ba41a2ea486c66a50c29c60d38c34a759 /root/coresight_test/main
> > 26b12a9d1a54ed2b0478cb0203435b76aabab3fb /usr/lib/a
> root@debian:~/coresight_test# perf buildid-list
> 0242d9154c78df1d8fe1d0512c36a236d0861a18 [kernel.kallsyms]
> b8c89e8ba41a2ea486c66a50c29c60d38c34a759 /root/coresight_test/main
> 26b12a9d1a54ed2b0478cb0203435b76aabab3fb /usr/lib/aarch64-linux-gnu/ld-
> 2.27.so
> 8fca7ed524c9469b065af83bc8a529fe7
Hi Mike,
On Fri, Nov 02, 2018 at 01:08:40PM +, Mike Leach wrote:
> Hi Leo,
>
> My understanding is that when we decode CoreSight trace - be it on the
> system that generated it, or off target device on a separate host
> system, we are using the dso files in .debug/ as these represent the
> me
Hi Al,
On Fri, Nov 02, 2018 at 12:08:04PM +, Al Grant wrote:
> > Now I still don't understand how the dso/map support "/proc/kallsyms" and
> > have no idea to fix this issue, though I spent some time to look into it.
>
> The way this is supported is that at record time, pseudo mmap records
>
Hi Leo,
My understanding is that when we decode CoreSight trace - be it on the
system that generated it, or off target device on a separate host
system, we are using the dso files in .debug/ as these represent the
memory layout at the time trace was recorded.
If I look into a recent session copie
> Now I still don't understand how the dso/map support "/proc/kallsyms" and
> have no idea to fix this issue, though I spent some time to look into it.
The way this is supported is that at record time, pseudo mmap records
are created for the kernel. But depending on permissions these might
not get
10 matches
Mail list logo
