On Tue, 28 Mar 2017 18:08:16 +0200
Alban Crequy wrote:
> Thanks for the review,
>
> On Tue, Mar 28, 2017 at 5:23 PM, Masami Hiramatsu wrote:
> > On Tue, 28 Mar 2017 15:52:22 +0200
> > Alban Crequy wrote:
> >
> >> When a kretprobe is installed on a kernel function, there is a maximum
> >> limit
On Tue, 28 Mar 2017 11:34:07 -0400
Steven Rostedt wrote:
> On Wed, 29 Mar 2017 00:23:35 +0900
> Masami Hiramatsu wrote:
>
> > > @@ -598,8 +601,10 @@ static int create_trace_kprobe(int argc, char **argv)
> > > {
> > > /*
> > >* Argument syntax:
> > > - * - Add kprobe: p[:[GRP/]EVENT] [M
Thanks for the review,
On Tue, Mar 28, 2017 at 5:23 PM, Masami Hiramatsu wrote:
> On Tue, 28 Mar 2017 15:52:22 +0200
> Alban Crequy wrote:
>
>> When a kretprobe is installed on a kernel function, there is a maximum
>> limit of how many calls in parallel it can catch (aka "maxactive"). A
>> kerne
On Wed, 29 Mar 2017 00:23:35 +0900
Masami Hiramatsu wrote:
> > @@ -598,8 +601,10 @@ static int create_trace_kprobe(int argc, char **argv)
> > {
> > /*
> > * Argument syntax:
> > -* - Add kprobe: p[:[GRP/]EVENT] [MOD:]KSYM[+OFFS]|KADDR [FETCHARGS]
> > -* - Add kretprobe: r[:[GR
On Tue, 28 Mar 2017 15:52:22 +0200
Alban Crequy wrote:
> When a kretprobe is installed on a kernel function, there is a maximum
> limit of how many calls in parallel it can catch (aka "maxactive"). A
> kernel module could call register_kretprobe() and initialize maxactive
> (see example in sample
"[PATCH v1]" I like your confidence, or lack of, that there isn't going
to be a v2 or v3 ;-)
Masami, what do you think of this?
-- Steve
On Tue, 28 Mar 2017 15:52:22 +0200
Alban Crequy wrote:
> When a kretprobe is installed on a kernel function, there is a maximum
> limit of how many calls i
When a kretprobe is installed on a kernel function, there is a maximum
limit of how many calls in parallel it can catch (aka "maxactive"). A
kernel module could call register_kretprobe() and initialize maxactive
(see example in samples/kprobes/kretprobe_example.c).
But that is not exposed to users
