[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100129092135.GE10878@elte.hu>
Date: Fri, 29 Jan 2010 10:21:35 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Masami Hiramatsu <mhiramat@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Fr??d??ric Weisbecker <fweisbec@...il.com>,
Steven Rostedt <rostedt@...dmis.org>
Cc: lkml <linux-kernel@...r.kernel.org>,
systemtap <systemtap@...rces.redhat.com>,
DLE <dle-develop@...ts.sourceforge.net>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Jim Keniston <jkenisto@...ibm.com>,
Mathieu Desnoyers <compudj@...stal.dyndns.org>,
Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH tracing/kprobes] kprobes: Disable booster when
CONFIG_PREEMPT=y
* Masami Hiramatsu <mhiramat@...hat.com> wrote:
> Disable kprobe booster when CONFIG_PREEMPT=y, because it can't ensure that
> all kernel threads preempted on kprobe's boosted slot run out from the slot
> even using freeze_processes().
hm, this really sucks as it makes preemptible kernels perform worse. Is there
no better solution?
> The booster on preemptive kernel will be resumed if synchronize_tasks() or
> something like that is introduced.
such as this one?
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists