linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Binoy Jayan <binoy.jayan@linaro.org>
Cc: linux-kernel@vger.kernel.org,
	Daniel Wagner <daniel.wagner@bmw-carit.de>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 0/2] *** Latency Histogram ***
Date: Thu, 28 Jul 2016 09:10:24 -0400	[thread overview]
Message-ID: <20160728131024.GA11666@home.goodmis.org> (raw)
In-Reply-To: <1469681535-25159-1-git-send-email-binoy.jayan@linaro.org>

On Thu, Jul 28, 2016 at 10:22:12AM +0530, Binoy Jayan wrote:
> Hi,
> 
> I was looking at these RT kernel patches and was wondering why it has
> not been upstreamed yet. I have made a few changes to these patches to
> make it compliant with upstream submission process. Also did a minimal
> testing on my msm board. Can some one from rt kernel team shed some
> light on why this is not upstreamed yet? Also if there some way to test

Note, Daniel did start work on upstreaming this previously:

 http://lkml.kernel.org/r/1430388385-29558-1-git-send-email-daniel.wagner@bmw-carit.de

There are a few things that do need to be cleaned up before this can go
upstream. Please coordinate any effort with Daniel, if you want to get this
rolling again. I'm not sure why the effort died last time. Could be because
something more important came up.

-- Steve


> this throroughly on a board with a high resolution timer running mainline
> (and not rt) kernel.
> 
> Binoy
> 
> Carsten Emde (1):
>   tracing: Add latency histograms
> 
> Yang Shi (1):
>   trace: Add missing tracer macros
> 
>  Documentation/trace/histograms.txt  |  186 ++++++
>  include/linux/hrtimer.h             |    3 +
>  include/linux/sched.h               |    6 +
>  include/trace/events/hist.h         |   74 +++
>  include/trace/events/latency_hist.h |  136 +++++
>  kernel/time/hrtimer.c               |   20 +
>  kernel/trace/Kconfig                |  104 ++++
>  kernel/trace/Makefile               |    4 +
>  kernel/trace/latency_hist.c         | 1091 +++++++++++++++++++++++++++++++++++
>  kernel/trace/trace_irqsoff.c        |    9 +
>  10 files changed, 1633 insertions(+)
>  create mode 100644 Documentation/trace/histograms.txt
>  create mode 100644 include/trace/events/hist.h
>  create mode 100644 include/trace/events/latency_hist.h
>  create mode 100644 kernel/trace/latency_hist.c
> 
> -- 
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> a Linux Foundation Collaborative Project

  parent reply	other threads:[~2016-07-28 13:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-28  4:52 [PATCH 0/2] *** Latency Histogram *** Binoy Jayan
2016-07-28  4:52 ` [PATCH 1/2] tracing: Add latency histograms Binoy Jayan
2016-07-28 18:51   ` Carsten Emde
2016-07-28  4:52 ` [PATCH 2/2] trace: Add missing tracer macros Binoy Jayan
2016-07-28 13:10 ` Steven Rostedt [this message]
2016-07-28 13:25   ` [PATCH 0/2] *** Latency Histogram *** Daniel Wagner

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=20160728131024.GA11666@home.goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=binoy.jayan@linaro.org \
    --cc=daniel.wagner@bmw-carit.de \
    --cc=linux-kernel@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).