From: Steven Rostedt <rostedt@goodmis.org>
To: Binoy Jayan <binoy.jayan@linaro.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Daniel Wagner <daniel.wagner@bmw-carit.de>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
Masami <masami.hiramatsu@linaro.org>
Subject: Re: [PATCH v4 3/3] tracing: Histogram for missed timer offsets
Date: Tue, 30 Aug 2016 10:15:27 -0400 [thread overview]
Message-ID: <20160830101527.3acd6ad6@gandalf.local.home> (raw)
In-Reply-To: <1472552924-22297-4-git-send-email-binoy.jayan@linaro.org>
On Tue, 30 Aug 2016 15:58:44 +0530
Binoy Jayan <binoy.jayan@linaro.org> wrote:
> +TRACE_EVENT(latency_hrtimer_interrupt,
> +
> + TP_PROTO(long long toffset, struct task_struct *curr,
> + struct task_struct *task),
> +
> + TP_ARGS(toffset, curr, task),
> +
> + TP_STRUCT__entry(
> + __field(long long, toffset)
> + __array(char, ccomm, TASK_COMM_LEN)
Can curr be different than current? If not, lets not record it.
-- Steve
> + __field(int, cprio)
> + __array(char, tcomm, TASK_COMM_LEN)
> + __field(int, tprio)
> + ),
next prev parent reply other threads:[~2016-08-30 14:15 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 [this message]
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
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=20160830101527.3acd6ad6@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=arnd@arndb.de \
--cc=binoy.jayan@linaro.org \
--cc=daniel.wagner@bmw-carit.de \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu@linaro.org \
--cc=mingo@redhat.com \
/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).