[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090422091645.GB18226@elte.hu>
Date: Wed, 22 Apr 2009 11:16:45 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Tim Abbott <tabbott@....EDU>
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>
Subject: Re: [PATCH 1/5] ftrace: use module notifier for function tracer
* Tim Abbott <tabbott@....EDU> wrote:
> On Sun, 19 Apr 2009, Rusty Russell wrote:
>
> > I think you need to do something else in general. Share the module_mutex for
> > the ftrace code? The ksplice guys have a similar issue, so maybe we should
> > generalize this into a "kernel_text" mutex?
>
> Yes, a kernel_text mutex is on my list of things to propose once
> Ksplice gets merged.
too late :-) These bits were written 1.5 months ago and are already
upstream:
3945dab: tracing, Text Edit Lock - SMP alternatives support
4460fda: tracing, Text Edit Lock - kprobes architecture independent support
0e39ac4: tracing, Text Edit Lock - Architecture Independent Code
I suspect ksplice could make use of text_mutex?
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