From: Ian Rogers <irogers@google.com>
To: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
Cc: y.karadz@gmail.com, acme@kernel.org, olsajiri@gmail.com,
rostedt@goodmis.org, linux-trace-devel@vger.kernel.org,
linux-perf-users@vger.kernel.org
Subject: Re: [RFC PATCH 0/3] trace-cruncher: Initial support for perf
Date: Thu, 24 Feb 2022 08:52:59 -0800 [thread overview]
Message-ID: <CAP-5=fVsQ2kGTvCDmovLWR00SDKQz635ftVmLphZcMM82sGKHA@mail.gmail.com> (raw)
In-Reply-To: <20220224163711.185308-1-tz.stoyanov@gmail.com>
On Thu, Feb 24, 2022 at 8:37 AM Tzvetomir Stoyanov (VMware)
<tz.stoyanov@gmail.com> wrote:
>
> Two major functionalities are introduced by this patch set:
> - VMA <-> function name resolving, using bfd library.
Just wanted to point out that perf is often not built against libbfd:
Please build perf against libbfd -
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911815
where long running addr2line is now the best performance solution:
https://lore.kernel.org/linux-perf-users/20210909112202.1947499-1-tonyg@leastfixedpoint.com/
The comment from the bug:
perf can link against libbfd if available, but the result is
undistributable as they are licenced under GPL v2 and v3+
respectively.
Thanks,
Ian
> - Support for Linux kernel perf framework, using perf library.
>
> This is still a work in progress. Depends on this patch, not yet merged:
> https://lore.kernel.org/linux-perf-users/20220221102628.43904-1-tz.stoyanov@gmail.com/
>
> Tzvetomir Stoyanov (VMware) (3):
> trace-cruncher: Logic for resolving address to function name
> trace-cruncher: Support for perf
> trace-cruncher: perf example
>
> examples/perf_sampling.py | 51 +++
> setup.py | 9 +-
> src/perfpy-utils.c | 699 ++++++++++++++++++++++++++++++
> src/perfpy-utils.h | 41 ++
> src/perfpy.c | 141 ++++++
> src/trace-obj-debug.c | 873 ++++++++++++++++++++++++++++++++++++++
> src/trace-obj-debug.h | 52 +++
> 7 files changed, 1865 insertions(+), 1 deletion(-)
> create mode 100755 examples/perf_sampling.py
> create mode 100644 src/perfpy-utils.c
> create mode 100644 src/perfpy-utils.h
> create mode 100644 src/perfpy.c
> create mode 100644 src/trace-obj-debug.c
> create mode 100644 src/trace-obj-debug.h
>
> --
> 2.34.1
>
prev parent reply other threads:[~2022-02-24 16:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 16:37 [RFC PATCH 0/3] trace-cruncher: Initial support for perf Tzvetomir Stoyanov (VMware)
2022-02-24 16:37 ` [RFC PATCH 1/3] trace-cruncher: Logic for resolving address to function name Tzvetomir Stoyanov (VMware)
2022-02-24 16:37 ` [RFC PATCH 2/3] trace-cruncher: Support for perf Tzvetomir Stoyanov (VMware)
2022-02-25 14:51 ` Arnaldo Carvalho de Melo
2022-02-25 15:38 ` Tzvetomir Stoyanov
2022-02-24 16:37 ` [RFC PATCH 3/3] trace-cruncher: perf example Tzvetomir Stoyanov (VMware)
2022-03-18 9:52 ` Yordan Karadzhov
2022-02-24 16:52 ` Ian Rogers [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='CAP-5=fVsQ2kGTvCDmovLWR00SDKQz635ftVmLphZcMM82sGKHA@mail.gmail.com' \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=olsajiri@gmail.com \
--cc=rostedt@goodmis.org \
--cc=tz.stoyanov@gmail.com \
--cc=y.karadz@gmail.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).