[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55B96B0A.2090003@iogearbox.net>
Date: Thu, 30 Jul 2015 02:08:42 +0200
From: Daniel Borkmann <daniel@...earbox.net>
To: Kaixu Xia <xiakaixu@...wei.com>, ast@...mgrid.com,
davem@...emloft.net, acme@...nel.org, mingo@...hat.com,
a.p.zijlstra@...llo.nl, masami.hiramatsu.pt@...achi.com,
jolsa@...nel.org
CC: wangnan0@...wei.com, linux-kernel@...r.kernel.org,
pi3orama@....com, hekuang@...wei.com
Subject: Re: [PATCH v4 0/4] bpf: Introduce the new ability of eBPF programs
to access hardware PMU counter
On 07/28/2015 01:17 PM, Kaixu Xia wrote:
> Previous patch v3 url:
> https://lkml.org/lkml/2015/7/23/203
...
> Kaixu Xia (3):
> bpf: Add new bpf map type to store the pointer to struct perf_event
> bpf: Implement function bpf_perf_event_read() that get the selected
> hardware PMU conuter
> samples/bpf: example of get selected PMU counter value
>
> Wang Nan (1):
> bpf: Make the bpf_prog_array_map more generic
So kernel/bpf/ patches are usually going via netdev tree as main development
happens there and to avoid cross tree conflicts, etc. Thus, please Cc also
netdev in the next iterations.
Maybe when these patches are in a perfect shape at some point, perf folks
provide their Acked-by(s) to the series to give their consent, and then this
should go via net-next? Or will this be organized differently?
> include/linux/bpf.h | 8 ++-
> include/linux/perf_event.h | 5 +-
> include/uapi/linux/bpf.h | 2 +
> kernel/bpf/arraymap.c | 161 ++++++++++++++++++++++++++++++++++++---------
> kernel/bpf/helpers.c | 36 ++++++++++
> kernel/bpf/syscall.c | 4 +-
> kernel/bpf/verifier.c | 15 +++++
> kernel/events/core.c | 21 +++++-
> kernel/trace/bpf_trace.c | 2 +
> samples/bpf/Makefile | 4 ++
> samples/bpf/bpf_helpers.h | 2 +
> samples/bpf/tracex6_kern.c | 26 ++++++++
> samples/bpf/tracex6_user.c | 67 +++++++++++++++++++
> 13 files changed, 316 insertions(+), 37 deletions(-)
> create mode 100644 samples/bpf/tracex6_kern.c
> create mode 100644 samples/bpf/tracex6_user.c
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists