From: Vince Weaver <vincent.weaver@maine.edu>
To: Ian Rogers <irogers@google.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
Jiri Olsa <olsajiri@gmail.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH V2] libperf evlist: Fix per-thread mmaps for multi-threaded targets
Date: Tue, 6 Sep 2022 17:17:14 -0400 (EDT) [thread overview]
Message-ID: <69bf3c5b-e3e8-9099-bd7b-b05beea7bd1f@maine.edu> (raw)
In-Reply-To: <CAP-5=fW3MLdzA01gWRx7yH-b=J4oqUTj9KMtrB0ZDpb0wucZ4A@mail.gmail.com>
On Tue, 6 Sep 2022, Ian Rogers wrote:
> > >> perf_evlist__set_mmap_first(evlist, map, overwrite);
> > >> } else {
> libperf CPU map code as I'd like to propose we start a libperf2 (with
> LPC coming up it'd be a good place to discuss this, there's also the
> office hours on Thursday). What I hope for libperf2 is that we can
> make its license the same as libbpf, so the code can be more widely
> included in projects.
If you did plan to do this, it might be nice to include some
representatives from groups that would be likely to use such a library.
This might include the PAPI library developers, and there are various
other tools (especially in the HPC area) who are coding to
perf_event_open() directly but probably would like to use a library
instead if possible.
Vince Weaver
vincent.weaver@maine.edu
next prev parent reply other threads:[~2022-09-06 21:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 11:42 Adrian Hunter
2022-09-06 12:53 ` Arnaldo Carvalho de Melo
2022-09-06 12:59 ` Jiri Olsa
2022-09-06 14:04 ` Adrian Hunter
2022-09-06 17:43 ` Ian Rogers
2022-09-06 21:17 ` Vince Weaver [this message]
2022-09-06 19:45 ` Jiri Olsa
2022-09-07 5:05 ` Adrian Hunter
2022-09-06 17:50 ` Namhyung Kim
2022-09-07 4:52 ` Adrian Hunter
2022-09-07 14:20 ` Jiri Olsa
2022-09-08 15:18 ` 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=69bf3c5b-e3e8-9099-bd7b-b05beea7bd1f@maine.edu \
--to=vincent.weaver@maine.edu \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=olsajiri@gmail.com \
--cc=peterz@infradead.org \
/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
all inboxes | Powered by JetHome®