- Original Message -
> From: "Steven Rostedt"
> To: "Chunyu Hu"
> Cc: "Namhyung Kim" , "LKML"
> Sent: Wednesday, June 29, 2016 4:03:33 AM
> Subject: Re: [PATCH V3] tracing: Make latency tracers fully support the
> set_
On Tue, 28 Jun 2016 04:03:12 -0400 (EDT)
Chunyu Hu wrote:
> Hello,
>
>
> Thanks for attention. It needs about three trace entries after the graph_entry
> of the filtered function, and the entries are all the sub call of the filtered
> function. As tracing_max_latency will be set to the last
> l
Hello,
- Original Message -
> From: "Namhyung Kim"
> To: "Chunyu Hu"
> Cc: "Steven Rostedt" , "LKML"
>
> Sent: Tuesday, June 28, 2016 1:20:02 PM
> Subject: Re: [PATCH V3] tracing: Make latency tracers fully support the
> se
Hello,
On Fri, Jun 24, 2016 at 7:55 PM, Chunyu Hu wrote:
> latency tracers(wakeup, wakeup_rt, wakeup_dl, irqsoff) can use the
> function_graph trace when display_graph trace option is set by user
> via tracefs. And currently the set_graph_notrace filter is not fully
> supported in latency tracers
latency tracers(wakeup, wakeup_rt, wakeup_dl, irqsoff) can use the
function_graph trace when display_graph trace option is set by user
via tracefs. And currently the set_graph_notrace filter is not fully
supported in latency tracers, only the graph_ret event can be filtered,
the graph_ent events wi
5 matches
Mail list logo
