From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 0/2] [GIT PULL] tracing: removal of ftrace_preempt_disable
Date: Tue, 8 Jun 2010 19:35:13 +0200 [thread overview]
Message-ID: <20100608173513.GA11585@elte.hu> (raw)
In-Reply-To: <20100604013506.159506222@goodmis.org>
* Steven Rostedt <rostedt@goodmis.org> wrote:
>
> Ingo,
>
> This bug has been around for a while, and it only causes
> missed preemption checks (nothing to crash the kernel). This can
> wait till 2.6.36.
>
> Please pull the latest tip/perf/core-3 tree, which can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/perf/core-3
>
>
> Steven Rostedt (2):
> tracing/sched: Make preempt_schedule() notrace
> tracing: Remove ftrace_preempt_disable/enable
>
> ----
> kernel/sched.c | 6 ++--
> kernel/trace/ftrace.c | 5 +--
> kernel/trace/ring_buffer.c | 38 ++++++-----------------------
> kernel/trace/trace.c | 5 +--
> kernel/trace/trace.h | 48 -------------------------------------
> kernel/trace/trace_clock.c | 5 +--
> kernel/trace/trace_events.c | 5 +--
> kernel/trace/trace_functions.c | 6 ++--
> kernel/trace/trace_sched_wakeup.c | 5 +--
> kernel/trace/trace_stack.c | 6 ++--
> 10 files changed, 27 insertions(+), 102 deletions(-)
Pulled, thanks a lot Steve!
Ingo
prev parent reply other threads:[~2010-06-08 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 1:35 Steven Rostedt
2010-06-04 1:35 ` [PATCH 1/2] tracing/sched: Make preempt_schedule() notrace Steven Rostedt
2010-06-04 1:35 ` [PATCH 2/2] tracing: Remove ftrace_preempt_disable/enable Steven Rostedt
2010-06-04 6:57 ` Lai Jiangshan
2010-06-08 17:35 ` 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=20100608173513.GA11585@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome