From: Robert Richter <rric@kernel.org>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>,
Jiri Olsa <jolsa@redhat.com>,
linux-kernel@vger.kernel.org, Robert Richter <rric@kernel.org>
Subject: [PATCH resent 0/4] perf tools: Persistent events, changes for perf tool integration
Date: Thu, 22 Aug 2013 16:44:01 +0200 [thread overview]
Message-ID: <1377182645-12922-1-git-send-email-rric@kernel.org> (raw)
This patch set contains userland changes necessary for out-of-the-box
support of persistent events. These patches are follow on patches of
the kernel patches I sent out today:
[PATCH 00/16] perf, persistent: Kernel updates for perf tool integration
Persistent events are always enabled kernel events. Buffers are mapped
readonly and multiple users are allowed. The persistent event flag of
the event attribute must be set to specify such an event.
The following changes to perf tools are necessary to support
persistent events. A way is needed to specify sysfs entries to set
event flags. For this a new syntax 'attr<num>' was added to the event
parser, see patch #3. We also need to change perf tools to mmap
persistent event buffers readonly.
All patches can be found here:
git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git persistent-v3
-Robert
Robert Richter (4):
perf tools: Rename flex conditions to avoid name conflicts
perf tools: Modify event parser to update event attribute by index
perf tools: Add attr<num> syntax to event parser
perf tools: Retry mapping buffers readonly on EACCES
tools/perf/builtin-record.c | 11 +++++---
tools/perf/builtin-top.c | 8 ++++--
tools/perf/perf.h | 1 +
tools/perf/tests/parse-events.c | 12 ++++++---
tools/perf/util/parse-events.c | 59 +++++++++++++++++++----------------------
tools/perf/util/parse-events.h | 12 ++++-----
tools/perf/util/parse-events.l | 56 +++++++++++++++++++++++---------------
tools/perf/util/parse-events.y | 24 ++++++++++-------
tools/perf/util/pmu.c | 32 +++++-----------------
tools/perf/util/pmu.h | 9 ++-----
tools/perf/util/pmu.l | 1 +
tools/perf/util/pmu.y | 18 ++++++++++---
12 files changed, 129 insertions(+), 114 deletions(-)
--
1.8.3.2
next reply other threads:[~2013-08-22 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 14:44 Robert Richter [this message]
2013-08-22 14:44 ` [PATCH resent 1/4] perf tools: Rename flex conditions to avoid name conflicts Robert Richter
2013-08-22 14:44 ` [PATCH resent 2/4] perf tools: Modify event parser to update event attribute by index Robert Richter
2013-08-22 14:44 ` [PATCH resent 3/4] perf tools: Add attr<num> syntax to event parser Robert Richter
2013-08-22 14:44 ` [PATCH resent 4/4] perf tools: Retry mapping buffers readonly on EACCES Robert Richter
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=1377182645-12922-1-git-send-email-rric@kernel.org \
--to=rric@kernel.org \
--cc=acme@infradead.org \
--cc=bp@alien8.de \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).