From: Rob Herring <robh@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@redhat.com>
Cc: linux-kernel@vger.kernel.org, Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Namhyung Kim <namhyung@kernel.org>,
Itaru Kitayama <itaru.kitayama@gmail.com>
Subject: [PATCH v8 0/4] libperf userspace counter access
Date: Wed, 14 Apr 2021 10:54:08 -0500 [thread overview]
Message-ID: <20210414155412.3697605-1-robh@kernel.org> (raw)
I'm resending just the libperf userspace counter access without the Arm
bits so hopefully it can be picked up for 5.13. The Arm bits seem to be
a never ending review filled with long periods of silence. :(
Prior versions are here[1][2][3][4][5][6][7][8].
Rob
[1] https://lore.kernel.org/r/20190822144220.27860-1-raphael.gault@arm.com/
[2] https://lore.kernel.org/r/20200707205333.624938-1-robh@kernel.org/
[3] https://lore.kernel.org/r/20200828205614.3391252-1-robh@kernel.org/
[4] https://lore.kernel.org/r/20200911215118.2887710-1-robh@kernel.org/
[5] https://lore.kernel.org/r/20201001140116.651970-1-robh@kernel.org/
[6] https://lore.kernel.org/r/20210114020605.3943992-1-robh@kernel.org/
[7] https://lore.kernel.org/r/20210311000837.3630499-1-robh@kernel.org/
[8] https://lore.kernel.org/r/20210413171606.1825808-1-robh@kernel.org/
Rob Herring (4):
tools/include: Add an initial math64.h
libperf: Add evsel mmap support
libperf: tests: Add support for verbose printing
libperf: Add support for user space counter access
tools/include/linux/math64.h | 75 ++++++++++++++++++++
tools/lib/perf/Documentation/libperf.txt | 3 +
tools/lib/perf/evsel.c | 80 +++++++++++++++++++++
tools/lib/perf/include/internal/evsel.h | 1 +
tools/lib/perf/include/internal/mmap.h | 3 +
tools/lib/perf/include/internal/tests.h | 32 +++++++++
tools/lib/perf/include/perf/evsel.h | 3 +
tools/lib/perf/libperf.map | 3 +
tools/lib/perf/mmap.c | 88 ++++++++++++++++++++++++
tools/lib/perf/tests/Makefile | 6 +-
tools/lib/perf/tests/test-evsel.c | 66 ++++++++++++++++++
11 files changed, 358 insertions(+), 2 deletions(-)
create mode 100644 tools/include/linux/math64.h
--
2.27.0
next reply other threads:[~2021-04-14 15:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 15:54 Rob Herring [this message]
2021-04-14 15:54 ` [PATCH v8 1/4] tools/include: Add an initial math64.h Rob Herring
2021-04-14 16:07 ` [PATCH v8 2/4] libperf: Add evsel mmap support Rob Herring
2021-04-14 16:41 ` Namhyung Kim
2021-04-14 16:53 ` Rob Herring
2021-04-14 17:45 ` Namhyung Kim
2021-04-14 18:02 ` Arnaldo Carvalho de Melo
2021-04-14 18:23 ` Arnaldo Carvalho de Melo
2021-04-14 19:14 ` Namhyung Kim
2021-04-15 19:37 ` Arnaldo Carvalho de Melo
2021-04-15 20:09 ` Rob Herring
2021-04-15 20:20 ` Arnaldo Carvalho de Melo
2021-04-14 16:07 ` [PATCH v8 3/4] libperf: tests: Add support for verbose printing Rob Herring
2021-04-14 16:07 ` [PATCH v8 4/4] libperf: Add support for user space counter access Rob Herring
2021-04-20 11:10 ` Arnaldo Carvalho de Melo
2021-04-14 19:20 ` [PATCH v8 0/4] libperf userspace " Jiri Olsa
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=20210414155412.3697605-1-robh@kernel.org \
--to=robh@kernel.org \
--cc=acme@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=itaru.kitayama@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).