Re: [PATCH bpf-next v2 0/3] bpf: implement bpf_send_signal() helper

On 05/22, Alexei Starovoitov wrote: > On 5/22/19 9:38 AM, Stanislav Fomichev wrote: > > On 05/21, Yonghong Song wrote: > >> This patch tries to solve the following specific use case. > >> > >> Currently, bpf program can already collect stack traces > >> through kernel function get_perf_callchain()

Re: [PATCH bpf-next v2 0/3] bpf: implement bpf_send_signal() helper

On 5/22/19 9:38 AM, Stanislav Fomichev wrote: > On 05/21, Yonghong Song wrote: >> This patch tries to solve the following specific use case. >> >> Currently, bpf program can already collect stack traces >> through kernel function get_perf_callchain() >> when certain events happens (e.g., cache miss

Re: [PATCH bpf-next v2 0/3] bpf: implement bpf_send_signal() helper

On 05/21, Yonghong Song wrote: > This patch tries to solve the following specific use case. > > Currently, bpf program can already collect stack traces > through kernel function get_perf_callchain() > when certain events happens (e.g., cache miss counter or > cpu clock counter overflows). But such

[PATCH bpf-next v2 0/3] bpf: implement bpf_send_signal() helper

This patch tries to solve the following specific use case. Currently, bpf program can already collect stack traces through kernel function get_perf_callchain() when certain events happens (e.g., cache miss counter or cpu clock counter overflows). But such stack traces are not enough for jitted pro

[RFC PATCH bpf-next v2 0/3] bpf: implement bpf_send_signal() helper

Currently, bpf program can already collect stack traces when certain events happens (e.g., cache miss counter or cpu clock counter overflows). These stack traces can be used for performance analysis. For jitted programs, e.g., hhvm (jited php), it is very hard to get the true stack trace in the