From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Carsten Emde <C.Emde@osadl.org>,
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: Wed, 13 Jan 2016 17:08:33 +0100 [thread overview]
Message-ID: <56967681.9070204@linutronix.de> (raw)
In-Reply-To: <20160113105135.3334856c@gandalf.local.home>
On 01/13/2016 04:51 PM, Steven Rostedt wrote:
> On Wed, 13 Jan 2016 16:45:26 +0100
> Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
>
>> Is it somehow possible to detect this kind of bugs at compile time? Is
>> there an easy way to do this?
>
> There should have been a warning. Wasn't there one?
Sorry, my bad. I didn't enable it… Yes, there is one.
>> What is blocking the latency-hist tracer from entering mainline?
>
> Has it been submitted. Like lots of things in -rt, it just takes the
> effort of pushing out an RFC for inclusion.
Not that I recall. But this means that there is nothing specific that
you are aware of that needs to be changed before RFC.
So, Carsten do you mind taking the latency-hist patch and submitting it
as RFC for upstream inclusion?
> -- Steve
>
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-01-13 16:08 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 [this message]
2016-01-15 11:30 ` Carsten Emde
2016-01-15 14:05 ` Steven Rostedt
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=56967681.9070204@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=C.Emde@osadl.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.