From: Steven Rostedt <rostedt@goodmis.org>
To: Carsten Emde <C.Emde@osadl.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>,
Linux RT Users <linux-rt-users@vger.kernel.org>
Subject: Re: trace/latency-hist: Consider new argument when probing the sched_switch tracer
Date: Fri, 15 Jan 2016 09:05:38 -0500 [thread overview]
Message-ID: <20160115090538.29674790@gandalf.local.home> (raw)
In-Reply-To: <5698D86F.607@osadl.org>
On Fri, 15 Jan 2016 12:30:55 +0100
Carsten Emde <C.Emde@osadl.org> wrote:
> So the question is whether you still encourage me to write the RFC for
> upstream inclusion of the current code after some polishing - maybe, in the
> hope that someone will come up with the framework during RFC discussion -
> or we better wait, since writing an RFC for hopeless code really doesn't
> make sense.
Note, the latency measurement code is basically the last code that is
practically untouched from what was in the original latency-tracer code
from the -rt patch. It's been on my todo list to update it for some
time. There's a few things lacking with it. I want to improve that.
Perhaps this should be done before pushing in a histogram
infrastructure on top of it. I'll move this up on my priority list.
-- Steve
prev parent reply other threads:[~2016-01-15 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 9:21 trace/latency-hist: Consider new argument when probing the sched_switch tracer Carsten Emde
2016-01-13 15:45 ` Sebastian Andrzej Siewior
2016-01-13 15:51 ` Steven Rostedt
2016-01-13 16:08 ` Sebastian Andrzej Siewior
2016-01-15 11:30 ` Carsten Emde
2016-01-15 14:05 ` Steven Rostedt [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=20160115090538.29674790@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).