From: Jiri Olsa <jolsa@redhat.com>
To: Jiri Olsa <jolsa@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
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: Re: [PATCHv4 0/4] perf tools: Allow to enable/disable events via control pipe
Date: Thu, 7 Jan 2021 13:12:40 +0100 [thread overview]
Message-ID: <20210107121240.GA1019522@krava> (raw)
In-Reply-To: <20201226232038.390883-1-jolsa@kernel.org>
On Sun, Dec 27, 2020 at 12:20:34AM +0100, Jiri Olsa wrote:
> 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
>
> v4 changes:
> - some of the patches got merged
> - rebased to latest perf/core
> - fixed changelogs
> - added 'ping' command
any reviews?
thanks,
jirka
>
> 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: Allow to enable/disable events via control file
> perf tools: Add evlist control command
> perf tools: Add stop control command
> perf tools: Add ping control command
>
> tools/perf/Documentation/perf-record.txt | 15 ++++++++++++---
> tools/perf/builtin-record.c | 13 +++++++------
> tools/perf/builtin-stat.c | 5 +++--
> tools/perf/util/evlist.c | 112 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++---
> tools/perf/util/evlist.h | 6 ++++++
> tools/perf/util/evsel_fprintf.c | 2 ++
> tools/perf/util/python-ext-sources | 1 +
> tools/perf/util/setup.py | 2 +-
> 8 files changed, 141 insertions(+), 15 deletions(-)
>
next prev parent reply other threads:[~2021-01-07 12:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-26 23:20 [PATCHv4 0/4] perf tools: Allow to enable/disable events via control pipe Jiri Olsa
2020-12-26 23:20 ` [PATCH 1/4] perf tools: Allow to enable/disable events via control file Jiri Olsa
2021-01-19 14:16 ` Arnaldo Carvalho de Melo
2021-01-19 17:34 ` Jiri Olsa
2020-12-26 23:20 ` [PATCH 2/4] perf tools: Add evlist control command Jiri Olsa
2020-12-26 23:20 ` [PATCH 3/4] perf tools: Add stop " Jiri Olsa
2020-12-26 23:20 ` [PATCH 4/4] perf tools: Add ping " Jiri Olsa
2021-01-07 12:12 ` Jiri Olsa [this message]
2021-01-08 6:10 ` [PATCHv4 0/4] perf tools: Allow to enable/disable events via control pipe Namhyung Kim
2021-01-19 14:30 ` 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=20210107121240.GA1019522@krava \
--to=jolsa@redhat.com \
--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=jolsa@kernel.org \
--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 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.