All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: Kaixu Xia <xiakaixu@huawei.com>,
	ast@plumgrid.com, davem@davemloft.net, acme@kernel.org,
	mingo@redhat.com, a.p.zijlstra@chello.nl,
	masami.hiramatsu.pt@hitachi.com, jolsa@kernel.org
Cc: wangnan0@huawei.com, linux-kernel@vger.kernel.org,
	pi3orama@163.com, hekuang@huawei.com
Subject: Re: [PATCH v4 0/4] bpf: Introduce the new ability of eBPF programs to access hardware PMU counter
Date: Thu, 30 Jul 2015 02:08:42 +0200	[thread overview]
Message-ID: <55B96B0A.2090003@iogearbox.net> (raw)
In-Reply-To: <1438082255-60683-1-git-send-email-xiakaixu@huawei.com>

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
>


  parent reply	other threads:[~2015-07-30  0:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28 11:17 [PATCH v4 0/4] bpf: Introduce the new ability of eBPF programs to access hardware PMU counter Kaixu Xia
2015-07-28 11:17 ` [PATCH v4 1/4] bpf: Make the bpf_prog_array_map more generic Kaixu Xia
2015-07-29 23:17   ` Daniel Borkmann
2015-07-30  1:44     ` Alexei Starovoitov
2015-07-31  8:50       ` xiakaixu
2015-07-31 15:46         ` Alexei Starovoitov
2015-07-28 11:17 ` [PATCH v4 2/4] bpf: Add new bpf map type to store the pointer to struct perf_event Kaixu Xia
2015-07-29 23:30   ` Daniel Borkmann
2015-07-30  1:45     ` Alexei Starovoitov
2015-07-28 11:17 ` [PATCH v4 3/4] bpf: Implement function bpf_perf_event_read() that get the selected hardware PMU conuter Kaixu Xia
2015-07-29 23:51   ` Daniel Borkmann
2015-07-28 11:17 ` [PATCH v4 4/4] samples/bpf: example of get selected PMU counter value Kaixu Xia
2015-07-29 23:56   ` Daniel Borkmann
2015-07-30  0:08 ` Daniel Borkmann [this message]
2015-07-30  1:50   ` [PATCH v4 0/4] bpf: Introduce the new ability of eBPF programs to access hardware PMU counter Alexei Starovoitov

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=55B96B0A.2090003@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=ast@plumgrid.com \
    --cc=davem@davemloft.net \
    --cc=hekuang@huawei.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@redhat.com \
    --cc=pi3orama@163.com \
    --cc=wangnan0@huawei.com \
    --cc=xiakaixu@huawei.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 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.