Re: [PATCH v5 0/6] enable creating [k,u]probe with perf_event_open

2018-04-09 Thread Alexei Starovoitov
On 4/9/18 9:45 PM, Ravi Bangoria wrote: Hi Song, On 12/07/2017 04:15 AM, Song Liu wrote: With current kernel, user space tools can only create/destroy [k,u]probes with a text-based API (kprobe_events and uprobe_events in tracefs). This approach relies on user space to clean up the [k,u]probe

Re: [PATCH v5 0/6] enable creating [k,u]probe with perf_event_open

2018-04-09 Thread Ravi Bangoria
Hi Song, On 12/07/2017 04:15 AM, Song Liu wrote: > With current kernel, user space tools can only create/destroy [k,u]probes > with a text-based API (kprobe_events and uprobe_events in tracefs). This > approach relies on user space to clean up the [k,u]probe after using them. > However, this is

Re: [PATCH v5 0/6] enable creating [k,u]probe with perf_event_open

2017-12-19 Thread Peter Zijlstra
Took 1-4, Thanks!

Re: [PATCH v5 0/6] enable creating [k,u]probe with perf_event_open

2017-12-19 Thread Song Liu
> On Dec 8, 2017, at 11:57 AM, Daniel Borkmann wrote: > > On 12/06/2017 11:45 PM, Song Liu wrote: >> Changes PATCH v4 to PATCH v5: >> Remove PERF_PROBE_CONFIG_IS_RETPROBE from uapi, use PMU_FORMAT_ATTR >> instead. >> >> Changes PATCH v3 to PATCH v4: >> Remove uapi

Re: [PATCH v5 0/6] enable creating [k,u]probe with perf_event_open

2017-12-08 Thread Daniel Borkmann
On 12/06/2017 11:45 PM, Song Liu wrote: > Changes PATCH v4 to PATCH v5: > Remove PERF_PROBE_CONFIG_IS_RETPROBE from uapi, use PMU_FORMAT_ATTR > instead. > > Changes PATCH v3 to PATCH v4: > Remove uapi define MAX_PROBE_FUNC_NAME_LEN, use KSYM_NAME_LEN instead. > Add flag

Re: [PATCH v5 0/6] enable creating [k,u]probe with perf_event_open

2017-12-07 Thread Philippe Ombredanne
Song, On Wed, Dec 6, 2017 at 11:45 PM, Song Liu wrote: > Changes PATCH v4 to PATCH v5: > Remove PERF_PROBE_CONFIG_IS_RETPROBE from uapi, use PMU_FORMAT_ATTR > instead. > > Changes PATCH v3 to PATCH v4: > Remove uapi define MAX_PROBE_FUNC_NAME_LEN, use KSYM_NAME_LEN

[PATCH v5 0/6] enable creating [k,u]probe with perf_event_open

2017-12-06 Thread Song Liu
Changes PATCH v4 to PATCH v5: Remove PERF_PROBE_CONFIG_IS_RETPROBE from uapi, use PMU_FORMAT_ATTR instead. Changes PATCH v3 to PATCH v4: Remove uapi define MAX_PROBE_FUNC_NAME_LEN, use KSYM_NAME_LEN instead. Add flag PERF_PROBE_CONFIG_IS_RETPROBE for config field of [k,u]probe. Optimize