On Thu, 25 Sep 2014 23:10:31 +
"Elliott, Robert (Server Storage)" wrote:
>
>
> > -Original Message-
> > From: Steven Rostedt [mailto:rost...@goodmis.org]
> ...
> > Does, this patch fix it for you?
> >
> > -- Steve
> ...
>
> > - if (type == TRACE_GRAPH_ENT)
> > - ret =
> -Original Message-
> From: Steven Rostedt [mailto:rost...@goodmis.org]
...
> Does, this patch fix it for you?
>
> -- Steve
...
> - if (type == TRACE_GRAPH_ENT)
> - ret = trace_seq_puts(s, "==>");
> - else
> + if (trace_flags & TRACE_ITER_LATENCY_FMT) {
On Wed, 24 Sep 2014 14:49:41 -0700
Andi Kleen wrote:
> "Elliott, Robert (Server Storage)" writes:
>
> > The function-graph tracer marks some interrupt handler functions
> > with ==> and <== labels.
>
> I'm not sure the marking is really that useful. Isn't it always obvious
> f
: Re: ftrace function-graph and interprocessor interrupts
>
> "Elliott, Robert (Server Storage)" writes:
>
> > The function-graph tracer marks some interrupt handler functions
> > with ==> and <== labels.
>
> I'm not sure the marki
"Elliott, Robert (Server Storage)" writes:
> The function-graph tracer marks some interrupt handler functions
> with ==> and <== labels.
I'm not sure the marking is really that useful. Isn't it always obvious
from the function names where an interrupt starts/end?
-Andi
--
a..
The function-graph tracer marks some interrupt handler functions
with ==> and <== labels.
10) |
sd_setup_read_write_cmnd [sd_mod]() {
10) | scsi_init_io() {
10) |
6 matches
Mail list logo