[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.1.10.0904221250280.24280@vinegar-pot.mit.edu>
Date: Wed, 22 Apr 2009 18:20:39 -0400 (EDT)
From: Tim Abbott <tabbott@....EDU>
To: Ingo Molnar <mingo@...e.hu>
cc: Rusty Russell <rusty@...tcorp.com.au>,
Steven Rostedt <rostedt@...dmis.org>,
linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Anders Kaseorg <andersk@....edu>,
Jeffrey B Arnold <jbarnold@....edu>,
Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
Masami Hiramatsu <mhiramat@...hat.com>
Subject: Re: [PATCH 1/5] ftrace: use module notifier for function tracer
On Wed, 22 Apr 2009, Ingo Molnar wrote:
> I suspect ksplice could make use of text_mutex?
Yes, this is what I was imagining. Thanks for pointing this out! I plan
to make Ksplice use this for the next version of the Ksplice patch series.
However, since Ksplice can be built as a module, we'll want to
EXPORT_SYMBOL_GPL(text_mutex). The comment above text_mutex's definition
suggests some people would prefer not to have modules patching the kernel
text, and so this point might be contentious. I've found support for
building Ksplice as a module to be a useful feature in case one needs to
use multiple different versions of Ksplice on the same system (e.g.
because the version built in to the kernel doesn't support a particular
patch).
-Tim Abbott
--
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