On Mon, 2017-02-13 at 10:04 +0900, Namhyung Kim wrote:
> On Fri, Feb 10, 2017 at 12:58:30PM -0600, Tom Zanussi wrote:
> > Hi Masami,
> >
> > On Fri, 2017-02-10 at 18:34 +0900, Masami Hiramatsu wrote:
> > > On Fri, 10 Feb 2017 13:16:17 +0900
> > > Namhyung Kim wrote:
> > >
> > > > >
> > >
On Mon, 13 Feb 2017 10:04:16 +0900
Namhyung Kim wrote:
> On Fri, Feb 10, 2017 at 12:58:30PM -0600, Tom Zanussi wrote:
> > Hi Masami,
> >
> > On Fri, 2017-02-10 at 18:34 +0900, Masami Hiramatsu wrote:
> > > On Fri, 10 Feb 2017 13:16:17 +0900
> > > Namhyung Kim wrote:
> > >
> > > > >
> >
On Fri, Feb 10, 2017 at 12:58:30PM -0600, Tom Zanussi wrote:
> Hi Masami,
>
> On Fri, 2017-02-10 at 18:34 +0900, Masami Hiramatsu wrote:
> > On Fri, 10 Feb 2017 13:16:17 +0900
> > Namhyung Kim wrote:
> >
> > > >
> > > > Example - wakeup latency
> > > >
> > > >
> > > > This bas
Hi Masami,
On Fri, 2017-02-10 at 18:34 +0900, Masami Hiramatsu wrote:
> On Fri, 10 Feb 2017 13:16:17 +0900
> Namhyung Kim wrote:
>
> > >
> > > Example - wakeup latency
> > >
> > >
> > > This basically implements the -RT latency_hist 'wakeup_latency'
> > > histogram using the
Hi Namhyung,
On Fri, 2017-02-10 at 13:16 +0900, Namhyung Kim wrote:
> Hi Tom,
>
> On Wed, Feb 08, 2017 at 11:24:56AM -0600, Tom Zanussi wrote:
> > This patchset adds support for 'inter-event' quantities to the trace
> > event subsystem. The most important example of inter-event quantities
> > ar
On Fri, 10 Feb 2017 13:16:17 +0900
Namhyung Kim wrote:
> >
> > Example - wakeup latency
> >
> >
> > This basically implements the -RT latency_hist 'wakeup_latency'
> > histogram using the synthetic events, variables, and actions
> > described. The output below is from a ru
Hi Tom,
On Wed, Feb 08, 2017 at 11:24:56AM -0600, Tom Zanussi wrote:
> This patchset adds support for 'inter-event' quantities to the trace
> event subsystem. The most important example of inter-event quantities
> are latencies, or the time differences between two events.
>
> One of the main mot
On Thu, 09 Feb 2017 11:18:32 -0600
Tom Zanussi wrote:
> I think it might make a lot of sense at this point to actually create a
> system-wide list of active triggers e.g. tracing/events/triggers or
> something like that. It's something I've kind of wanted anyway, and
> would be really useful if
Hi Frank,
On Thu, 2017-02-09 at 09:46 -0500, Frank Ch. Eigler wrote:
> Hi, Tom -
>
>
> tom.zanussi wrote:
>
> > [...]
> >> Hmm, this looks a bit hard to understand, I guess that onmatch() means
> >> "if there is an event which has ts0 variable and the event's key matches
> >> this key, take som
On Thu, 2017-02-09 at 23:18 +0900, Masami Hiramatsu wrote:
> Hi Tom,
>
> On Wed, 08 Feb 2017 19:14:22 -0600
> Tom Zanussi wrote:
>
> > > > I'm submitting the patchset (based on tracing/for-next) as an RFC not
> > > > only to get comments, but because there are still some problems I
> > > > haven
Hi, Tom -
tom.zanussi wrote:
> [...]
>> Hmm, this looks a bit hard to understand, I guess that onmatch() means
>> "if there is an event which has ts0 variable and the event's key matches
>> this key, take some action".
>
> Yes, that's pretty much it. It's essentially shorthand for this kind of
Hi Tom,
On Wed, 08 Feb 2017 19:14:22 -0600
Tom Zanussi wrote:
> > > I'm submitting the patchset (based on tracing/for-next) as an RFC not
> > > only to get comments, but because there are still some problems I
> > > haven't fixed yet...
> > >
> > > Here are some examples that should make things
On Wed, 08 Feb 2017 17:28:50 -0600
Tom Zanussi wrote:
> On Wed, 2017-02-08 at 15:01 -0500, Steven Rostedt wrote:
> > On Wed, 8 Feb 2017 11:24:56 -0600
> > Tom Zanussi wrote:
> >
> > > # echo 'wakeup_latency lat=sched_switch:wakeup_lat \
> > >pid=sched_switch:w
Hi Masami,
On Thu, 2017-02-09 at 08:13 +0900, Masami Hiramatsu wrote:
> Hi Tom,
>
> On Wed, 8 Feb 2017 11:24:56 -0600
> Tom Zanussi wrote:
>
> > This patchset adds support for 'inter-event' quantities to the trace
> > event subsystem. The most important example of inter-event quantities
> > a
Hi Steve,
On Wed, 2017-02-08 at 15:01 -0500, Steven Rostedt wrote:
> On Wed, 8 Feb 2017 11:24:56 -0600
> Tom Zanussi wrote:
>
> > # echo 'wakeup_latency lat=sched_switch:wakeup_lat \
> >pid=sched_switch:woken_pid \
> >prio=sched_switch
On Wed, 2017-02-08 at 15:01 -0500, Steven Rostedt wrote:
> On Wed, 8 Feb 2017 11:24:56 -0600
> Tom Zanussi wrote:
>
> > # echo 'wakeup_latency lat=sched_switch:wakeup_lat \
> >pid=sched_switch:woken_pid \
> >prio=sched_switch:woken_prio
Hi Tom,
On Wed, 8 Feb 2017 11:24:56 -0600
Tom Zanussi wrote:
> This patchset adds support for 'inter-event' quantities to the trace
> event subsystem. The most important example of inter-event quantities
> are latencies, or the time differences between two events.
Great! This is what I dream!
On Wed, 8 Feb 2017 11:24:56 -0600
Tom Zanussi wrote:
> # echo 'wakeup_latency lat=sched_switch:wakeup_lat \
>pid=sched_switch:woken_pid \
>prio=sched_switch:woken_prio' >> \
> /sys/kernel/debug/tracing/synthetic_events
I ap
This patchset adds support for 'inter-event' quantities to the trace
event subsystem. The most important example of inter-event quantities
are latencies, or the time differences between two events.
One of the main motivations for adding this capability is to provide a
general-purpose base that ex
19 matches
Mail list logo