From: Masami Hiramatsu <masami.hiramatsu@linaro.org>
To: Daniel Wagner <daniel.wagner@bmw-carit.de>
Cc: Binoy Jayan <binoy.jayan@linaro.org>,
"Steven Rostedt (Red Hat)" <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/3] *** Latency histograms - IRQSOFF,PREEMPTOFF ***
Date: Tue, 30 Aug 2016 21:02:13 +0900 [thread overview]
Message-ID: <CAA93ih3-WUZakRuXtur6Ac9XELnEzfRuF9gJ8kn2PPi8+nxD_A@mail.gmail.com> (raw)
In-Reply-To: <dbbb4a5c-50ff-2da0-c2bb-166dee1532ea@bmw-carit.de>
2016-08-30 20:39 GMT+09:00 Daniel Wagner <daniel.wagner@bmw-carit.de>:
> 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 :)
Good idea! And also, for both patch, could you show the output examples?
It might help people to imagine what it provides.
Thank you,
--
Masami Hiramatsu
prev parent reply other threads:[~2016-08-30 12:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 10:28 [PATCH v4 0/3] *** Latency histograms - IRQSOFF,PREEMPTOFF *** Binoy Jayan
2016-08-30 10:28 ` [PATCH v4 1/3] tracing: Deference pointers without RCU checks Binoy Jayan
2016-08-30 10:28 ` [PATCH v4 2/3] tracing: Add trace_irqsoff tracepoints Binoy Jayan
2016-08-30 11:30 ` Daniel Wagner
2016-08-30 11:49 ` Binoy Jayan
2016-08-30 14:08 ` Steven Rostedt
2016-08-31 11:39 ` Binoy Jayan
2016-08-30 10:28 ` [PATCH v4 3/3] tracing: Histogram for missed timer offsets Binoy Jayan
2016-08-30 10:50 ` Masami Hiramatsu
2016-09-02 12:41 ` Binoy Jayan
2016-09-02 15:54 ` Masami Hiramatsu
2016-08-30 14:15 ` Steven Rostedt
2016-08-31 11:34 ` Binoy Jayan
2016-08-31 12:42 ` Steven Rostedt
2016-08-30 11:39 ` [PATCH v4 0/3] *** Latency histograms - IRQSOFF,PREEMPTOFF *** Daniel Wagner
2016-08-30 12:02 ` Masami Hiramatsu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93ih3-WUZakRuXtur6Ac9XELnEzfRuF9gJ8kn2PPi8+nxD_A@mail.gmail.com \
--to=masami.hiramatsu@linaro.org \
--cc=arnd@arndb.de \
--cc=binoy.jayan@linaro.org \
--cc=daniel.wagner@bmw-carit.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).