From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Clark Williams <williams@redhat.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Song Liu <songliubraving@fb.com>, Wang Nan <wangnan0@huawei.com>
Subject: [RFC PATCHSET] Implement --switch-output-events
Date: Mon, 27 Apr 2020 18:19:28 -0300 [thread overview]
Message-ID: <20200427211935.25789-1-acme@kernel.org> (raw)
Hi guys,
Please take a look, the example provided is too simple, using
'perf probe' to put probes in specific places in some workload to then
get any other event close to the time the trigger hits comes to mind as
well, using the signal was just to reuse the pre-existing logic and keep
the patchkit small.
Its available at:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git perf/switch-output-event
Best regards,
- Arnaldo
Arnaldo Carvalho de Melo (7):
perf record: Move sb_evlist to 'struct record'
perf top: Move sb_evlist to 'struct perf_top'
perf bpf: Decouple creating the evlist from adding the SB event
perf bpf: Decouple creating the evlist from adding the SB event
perf parse-events: Add parse_events_option() variant that creates
evlist
perf evlist: Allow reusing the side band thread for more purposes
perf record: Introduce --switch-output-event
tools/perf/Documentation/perf-record.txt | 13 ++++++
tools/perf/builtin-record.c | 55 +++++++++++++++++++++---
tools/perf/builtin-top.c | 20 ++++++---
tools/perf/util/bpf-event.c | 3 +-
tools/perf/util/bpf-event.h | 7 ++-
tools/perf/util/evlist.c | 39 +++++++++++------
tools/perf/util/evlist.h | 3 +-
tools/perf/util/parse-events.c | 23 ++++++++++
tools/perf/util/parse-events.h | 1 +
tools/perf/util/top.h | 2 +-
10 files changed, 133 insertions(+), 33 deletions(-)
--
2.21.1
next reply other threads:[~2020-04-27 21:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 21:19 Arnaldo Carvalho de Melo [this message]
2020-04-27 21:19 ` [PATCH 1/7] perf record: Move sb_evlist to 'struct record' Arnaldo Carvalho de Melo
2020-04-27 21:19 ` [PATCH 2/7] perf top: Move sb_evlist to 'struct perf_top' Arnaldo Carvalho de Melo
2020-04-27 21:19 ` [PATCH 3/7] perf bpf: Decouple creating the evlist from adding the SB event Arnaldo Carvalho de Melo
2020-04-27 21:19 ` [PATCH 4/7] " Arnaldo Carvalho de Melo
2020-04-28 9:48 ` Jiri Olsa
2020-04-28 17:21 ` Arnaldo Carvalho de Melo
2020-04-27 21:19 ` [PATCH 5/7] perf parse-events: Add parse_events_option() variant that creates evlist Arnaldo Carvalho de Melo
2020-04-27 21:19 ` [PATCH 6/7] perf evlist: Allow reusing the side band thread for more purposes Arnaldo Carvalho de Melo
2020-04-27 21:19 ` [PATCH 7/7] perf record: Introduce --switch-output-event Arnaldo Carvalho de Melo
2020-04-28 9:48 ` Jiri Olsa
2020-04-28 12:16 ` Arnaldo Carvalho de Melo
2020-04-28 13:22 ` Jiri Olsa
2020-04-28 18:05 ` Arnaldo Carvalho de Melo
2020-04-29 8:18 ` 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=20200427211935.25789-1-acme@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=songliubraving@fb.com \
--cc=tglx@linutronix.de \
--cc=wangnan0@huawei.com \
--cc=williams@redhat.com \
/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).