[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dbbb4a5c-50ff-2da0-c2bb-166dee1532ea@bmw-carit.de>
Date: Tue, 30 Aug 2016 13:39:43 +0200
From: Daniel Wagner <daniel.wagner@...-carit.de>
To: Binoy Jayan <binoy.jayan@...aro.org>,
"Steven Rostedt (Red Hat)" <rostedt@...dmis.org>
CC: Ingo Molnar <mingo@...hat.com>, Arnd Bergmann <arnd@...db.de>,
<linux-kernel@...r.kernel.org>,
Masami <masami.hiramatsu@...aro.org>
Subject: Re: [PATCH v4 0/3] *** Latency histograms - IRQSOFF,PREEMPTOFF ***
Hi Binoy,
On 08/30/2016 12:28 PM, Binoy Jayan wrote:
> Examples of triggers:
> echo 'hist:key=latency.log2:val=hitcount:sort=latency' > /sys/kernel/debug/tracing/events/latency/latency_preempt/trigger
> echo 'hist:key=cpu,latency:val=hitcount:sort=latency if cpu==1' > /sys/kernel/debug/tracing/events/latency/latency_preempt/trigger
> echo 'hist:key=ltype,cpu:val=latency:sort=ltype,cpu if ltype==0' > /sys/kernel/debug/tracing/events/latency/latency_preempt/trigger
>
> Histogram output:
> cat /sys/kernel/debug/tracing/events/latency/latency_preempt/hist
Could you also add couple of test cases to
tools/testing/selftests/ftrace/test.d/trigger?
Especially the sorting thing you mentioned in the other mail? Obviously
first we need to figure out what is the expected behavior of it :)
cheers,
daniel
Powered by blists - more mailing lists