From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@osdl.org>, Mike Mason <mmlnx@us.ibm.com>,
Dipankar Sarma <dipankar@in.ibm.com>,
David Smith <dsmith@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Adrian Bunk <adrian.bunk@movial.fi>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [patch 1/4] Markers - depends on not PREEMPT_RCU
Date: Thu, 20 Mar 2008 12:49:41 -0700 [thread overview]
Message-ID: <20080320194941.GD9570@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080320190335.GA12770@elte.hu>
On Thu, Mar 20, 2008 at 08:03:38PM +0100, Ingo Molnar wrote:
>
> * Mathieu Desnoyers <mathieu.desnoyers@polymtl.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
next prev parent reply other threads:[~2008-03-20 19:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 0:27 [patch 0/4] Markers updates for 2.6.25-rc6 Mathieu Desnoyers
2008-03-20 0:27 ` [patch 1/4] Markers - depends on not PREEMPT_RCU Mathieu Desnoyers
2008-03-20 19:03 ` Ingo Molnar
2008-03-20 19:49 ` Paul E. McKenney [this message]
2008-03-20 0:27 ` [patch 2/4] Markers - Update preempt_disable. call_rcu, rcu_barrier comments Mathieu Desnoyers
2008-03-20 0:27 ` [patch 3/4] Markers - Remove ACCESS_ONCE Mathieu Desnoyers
2008-03-20 0:27 ` [patch 4/4] Markers Support for Proprierary Modules Mathieu Desnoyers
2008-03-20 5:35 ` Rusty Russell
2008-03-20 12:30 ` Mathieu Desnoyers
2008-03-20 8:38 ` Christoph Hellwig
2008-03-20 19:12 ` Ingo Molnar
2008-03-20 19:18 ` Jon Masters
2008-03-20 22:15 ` Ingo Molnar
2008-03-20 20:17 ` Frank Ch. Eigler
2008-03-20 22:05 ` Ingo Molnar
2008-03-20 22:24 ` Mathieu Desnoyers
2008-03-20 22:22 ` Mathieu Desnoyers
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=20080320194941.GD9570@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=adrian.bunk@movial.fi \
--cc=akpm@linux-foundation.org \
--cc=akpm@osdl.org \
--cc=dipankar@in.ibm.com \
--cc=dsmith@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=mmlnx@us.ibm.com \
--cc=rostedt@goodmis.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.