From: Jiri Olsa <jolsa@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Michael Petlan <mpetlan@redhat.com>,
Ian Rogers <irogers@google.com>,
Stephane Eranian <eranian@google.com>,
Alexei Budankov <abudankov@huawei.com>
Subject: [PATCHv3 0/4] perf tools: Allow to enable/disable events via control pipe
Date: Wed, 16 Dec 2020 09:39:10 +0100 [thread overview]
Message-ID: <20201216083914.47215-1-jolsa@kernel.org> (raw)
hi,
adding support to enable/disable specific events via control
file via following commands:
# echo 'enable sched:sched_process_fork' > control
# echo 'disabled sched:sched_process_fork' > control
v3 changes:
- use ' ' instead of '-' in syntax and add command argument
processing [Arnaldo]
- add options to evlist [Arnaldo]
- add man page changes
v2 changes:
- added acks
- change list to evlist [Arnaldo]
- add evlist-verbose command [Arnaldo]
- add '' to enale-/disable- error message
The code is available in here:
git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
perf/control
thanks,
jirka
---
Jiri Olsa (4):
perf tools: Reformat record's control fd man text
perf tools: Add evlist__disable_evsel/evlist__enable_evsel
perf tools: Allow to enable/disable events via control file
perf tools: Add evlist control command
tools/perf/Documentation/perf-record.txt | 23 +++++++++++----
tools/perf/builtin-record.c | 9 ++----
tools/perf/builtin-stat.c | 3 +-
tools/perf/util/evlist.c | 173 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++----
tools/perf/util/evlist.h | 4 +++
tools/perf/util/evsel_fprintf.c | 2 ++
tools/perf/util/python-ext-sources | 1 +
tools/perf/util/setup.py | 2 +-
8 files changed, 197 insertions(+), 20 deletions(-)
next reply other threads:[~2020-12-16 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 8:39 Jiri Olsa [this message]
2020-12-16 8:39 ` [PATCH 1/4] perf tools: Reformat record's control fd man text Jiri Olsa
2020-12-16 8:39 ` [PATCH 2/4] perf tools: Add evlist__disable_evsel/evlist__enable_evsel Jiri Olsa
2020-12-16 8:39 ` [PATCH 3/4] perf tools: Allow to enable/disable events via control file Jiri Olsa
2020-12-16 8:39 ` [PATCH 4/4] perf tools: Add evlist control command 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=20201216083914.47215-1-jolsa@kernel.org \
--to=jolsa@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=abudankov@huawei.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=mpetlan@redhat.com \
--cc=namhyung@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).