Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1195682 > unrolled thread

Re: [PATCH v4 0/4] bpf: Introduce the new ability of eBPF programs to access hardware PMU counter

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH v4 0/4] bpf: Introduce the new ability of eBPF programs to  access hardware PMU counter Alexei Starovoitov <ast@plumgrid.com> - 2015-07-30 04:00 +0200

#1195682 — Re: [PATCH v4 0/4] bpf: Introduce the new ability of eBPF programs to access hardware PMU counter

On 7/29/15 5:08 PM, Daniel Borkmann wrote:
> 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?

In this case it looks that amount of kernel/bpf/ changes is higher than
perf related. Also it looks like addition of bpf_perf_event_read()
helper also won't affect anything on perf side, so in this case I think
net-next tree is indeed a better fit.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [standalone]

Back to top | Article view | linux.kernel

csiph-web