From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Tzvetomir Stoyanov <tz.stoyanov@gmail.com>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Jiri Olsa <olsajiri@gmail.com>, Ian Rogers <irogers@google.com>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v2] libperf: Add API for allocating new thread map
Date: Tue, 22 Feb 2022 21:21:24 -0300 [thread overview]
Message-ID: <YhV+BOp0A+aqavlc@kernel.org> (raw)
In-Reply-To: <CAPpZLN7Qmgsm6ptthvsjgcqgMQd1tnuX=ohHBcPAQ4zu4VVkrw@mail.gmail.com>
Em Tue, Feb 22, 2022 at 04:32:05AM +0200, Tzvetomir Stoyanov escreveu:
> On Mon, Feb 21, 2022 at 10:21 PM Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com> wrote:
> > On February 21, 2022 4:46:49 PM GMT-03:00, Jiri Olsa <olsajiri@gmail.com> wrote:
> > >On Mon, Feb 21, 2022 at 12:26:28PM +0200, Tzvetomir Stoyanov (VMware) wrote:
> > >looks good, would you also find useful in your use case the comm support
> > >in thread_map? the thread_map__read_comms function? we could move it from
> > >perf to libperf
> > IOW: we're happy that you're working on libperf, so feel encouraged
> > to move things from tools/perf/util/ to tools/lib/perf/ if you find
> > a supporting use case, brownie points if you also add an entry to
> > tools/perf/tests/, AKA 'perf test'.
> Thanks, I see that there is a lot of functionality that could be moved
> from perf to libperf and which will be useful for the library users.
> We are going to use libperf in trace-cruncher,
> https://github.com/vmware/trace-cruncher, as an interface to perf.
Cool, so as you go on adding functionality to trace cruncher and notice
that something that is in tools/perf/util/ that is usable, please submit
patches to move things to tools/lib/perf/, adding tests to 'perf test'
as you go.
Thanks a lot!
- Arnaldo
next prev parent reply other threads:[~2022-02-23 0:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 10:26 [PATCH v2] libperf: Add API for allocating new thread map Tzvetomir Stoyanov (VMware)
2022-02-21 19:46 ` Jiri Olsa
2022-02-21 20:07 ` Arnaldo Carvalho de Melo
2022-02-22 2:32 ` Tzvetomir Stoyanov
2022-02-23 0:21 ` Arnaldo Carvalho de Melo [this message]
2022-02-23 9:08 ` Tzvetomir Stoyanov
2022-02-23 13:02 ` Jiri Olsa
2022-02-23 15:47 ` Tzvetomir Stoyanov
2022-02-23 18:06 ` Jiri Olsa
2022-02-22 2:21 ` Tzvetomir Stoyanov
2022-02-23 0:22 ` Arnaldo Carvalho de Melo
2022-02-23 13:31 ` Jiri Olsa
2022-02-23 15:30 ` Arnaldo Carvalho de Melo
2022-03-21 11:10 ` Tzvetomir Stoyanov
2022-03-21 21:10 ` Arnaldo Carvalho de Melo
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=YhV+BOp0A+aqavlc@kernel.org \
--to=acme@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=irogers@google.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=olsajiri@gmail.com \
--cc=tz.stoyanov@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.