From: Alexei Starovoitov <ast@fb.com>
To: "David S . Miller" <davem@davemloft.net>
Cc: Peter Zijlstra <peterz@infradead.org>,
Brendan Gregg <bgregg@netflix.com>,
Daniel Borkmann <daniel@iogearbox.net>, Teng Qin <qinteng@fb.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kernel-team@fb.com>
Subject: [PATCH net-next 0/2] perf, bpf: add support for HW_CACHE and RAW events
Date: Mon, 22 May 2017 15:48:38 -0700 [thread overview]
Message-ID: <20170522224840.810121-1-ast@fb.com> (raw)
Patch 1: add support for HW_CACHE and RAW perf events to bpf:
- similar to PERF_TYPE_RAW and PERF_TYPE_HARDWARE allow PERF_TYPE_HW_CACHE
events to be accessed via bpf_perf_event_read()
- similar to PERF_TYPE_HARDWARE and PERF_TYPE_SOFTWARE allow bpf programs
to attch to PERF_TYPE_HW_CACHE and PERF_TYPE_RAW events as
BPF_PROG_TYPE_PERF_EVENT program type
Patch 2: add tests for HW_CACHE and RAW events
---
Peter,
please review patch 1. It looks trivial and as far as
we can see nothing else needed. The existing perf+bpf infra
covers it just fine.
Thanks!
Teng Qin (2):
perf, bpf: add support for HW_CACHE and RAW events
samples/bpf: add samples for HW_CACHE / RAW events
kernel/bpf/arraymap.c | 1 +
kernel/events/core.c | 4 +-
kernel/trace/bpf_trace.c | 1 +
samples/bpf/bpf_helpers.h | 2 +-
samples/bpf/trace_event_user.c | 46 +++++++++++-
samples/bpf/tracex6_kern.c | 28 ++++++--
samples/bpf/tracex6_user.c | 155 +++++++++++++++++++++++++++++++----------
7 files changed, 187 insertions(+), 50 deletions(-)
--
2.9.3
next reply other threads:[~2017-05-22 22:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 22:48 Alexei Starovoitov [this message]
2017-05-22 22:48 ` [PATCH net-next 1/2] perf, bpf: add support for HW_CACHE and RAW events Alexei Starovoitov
2017-05-23 7:42 ` Peter Zijlstra
2017-05-23 14:38 ` Alexei Starovoitov
2017-05-23 16:31 ` Peter Zijlstra
2017-05-23 17:05 ` Alexei Starovoitov
2017-05-22 22:48 ` [PATCH net-next 2/2] samples/bpf: add samples for HW_CACHE / " Alexei Starovoitov
2017-05-22 23:26 ` David Miller
2017-05-22 23:35 ` Alexei Starovoitov
2017-05-22 23:40 ` David Miller
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=20170522224840.810121-1-ast@fb.com \
--to=ast@fb.com \
--cc=bgregg@netflix.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=qinteng@fb.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).