From: Ingo Molnar <mingo@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 0/3 v2] [GIT PULL][3.9] tracing: Fixes with flags and latency tracers
Date: Mon, 18 Mar 2013 09:49:13 +0100 [thread overview]
Message-ID: <20130318084913.GD17959@gmail.com> (raw)
In-Reply-To: <20130315050616.512983245@goodmis.org>
* Steven Rostedt <rostedt@goodmis.org> wrote:
>
> Ingo,
>
> Here's take two of the last patch series I sent. The only difference
> with this series is that I encapsulate the max_tr reference with
> the #ifdef CONFIG_TRACER_MAX_TRACE. Other than that, it's the same.
>
> Here's the recap:
>
> The first patch fixes a long standing bug where the changing of
> the trace options has absolutely no protection against multiple
> changers. Luckily, this is something that requires human (root)
> action, and is usually performed by a single individual. But as
> scripts are starting to become more active, this bug is bound to
> be triggered.
>
> The second patch is a bug where the setting of the overwrite flag
> can cause the max and normal buffers to get out of sync. This
> is more predomitinant with the 3.9 snapshot feature, but still
> has an affect on the latency tracers. Which bring us to the third
> patch.
>
> The third patch I found out that disabling overwrite to the buffers
> screws with the latency tracers. If the buffer is in produce consumer
> mode, the irqsoff tracer and friends wont show any output at all.
> This was a bit frustrating to figure out.
>
> Hopefully this time it's good.
>
> Thanks,
>
> -- Steve
>
> Please pull the latest tip/perf/urgent-2 tree, which can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
> tip/perf/urgent-2
>
> Head SHA1: 613f04a0f51e6e68ac6fe571ab79da3c0a5eb4da
>
>
> Steven Rostedt (Red Hat) (3):
> tracing: Protect tracer flags with trace_types_lock
> tracing: Keep overwrite in sync between regular and snapshot buffers
> tracing: Prevent buffer overwrite disabled for latency tracers
>
> ----
> kernel/trace/trace.c | 56 +++++++++++++++++++++++++++++--------
> kernel/trace/trace.h | 6 ++++
> kernel/trace/trace_irqsoff.c | 19 +++++++++----
> kernel/trace/trace_sched_wakeup.c | 18 ++++++++----
> 4 files changed, 78 insertions(+), 21 deletions(-)
Pulled, thanks Steve!
Ingo
prev parent reply other threads:[~2013-03-18 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 5:06 [PATCH 0/3 v2] [GIT PULL][3.9] tracing: Fixes with flags and latency tracers Steven Rostedt
2013-03-15 5:06 ` [PATCH 1/3 v2] tracing: Protect tracer flags with trace_types_lock Steven Rostedt
2013-03-15 5:06 ` [PATCH 2/3 v2] tracing: Keep overwrite in sync between regular and snapshot buffers Steven Rostedt
2013-03-15 5:06 ` [PATCH 3/3 v2] tracing: Prevent buffer overwrite disabled for latency tracers Steven Rostedt
2013-03-18 8:49 ` Ingo Molnar [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=20130318084913.GD17959@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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