[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080320194941.GD9570@linux.vnet.ibm.com>
Date: Thu, 20 Mar 2008 12:49:41 -0700
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
Christoph Hellwig <hch@...radead.org>,
Andrew Morton <akpm@...l.org>, Mike Mason <mmlnx@...ibm.com>,
Dipankar Sarma <dipankar@...ibm.com>,
David Smith <dsmith@...hat.com>,
Steven Rostedt <rostedt@...dmis.org>,
Adrian Bunk <adrian.bunk@...ial.fi>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [patch 1/4] Markers - depends on not PREEMPT_RCU
On Thu, Mar 20, 2008 at 08:03:38PM +0100, Ingo Molnar wrote:
>
> * Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca> wrote:
>
> > +++ linux-2.6-lttng/init/Kconfig 2008-03-19 18:27:43.000000000 -0400
> > @@ -742,6 +742,7 @@ config PROFILING
> >
> > config MARKERS
> > bool "Activate markers"
> > + depends on !PREEMPT_RCU
> > help
>
> Ugh, NACK. Please solve this properly... What kind of kernel
> infrastructure is it what disables itself in the presence of another
> piece of kernel infrastructure?
This is a reminder to me to get going on call_rcu_sched(). Until
I get that done and in, they don't have what they need to work
with preemptable RCU. :-/
Thanx, Paul
--
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