[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20100304203649.GJ6768@linux.vnet.ibm.com>
Date: Thu, 4 Mar 2010 12:36:49 -0800
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: linux-kernel@...r.kernel.org, laijs@...fujitsu.com,
dipankar@...ibm.com, akpm@...ux-foundation.org,
mathieu.desnoyers@...ymtl.ca, josh@...htriplett.org,
dvhltc@...ibm.com, niv@...ibm.com, tglx@...utronix.de,
peterz@...radead.org, rostedt@...dmis.org, Valdis.Kletnieks@...edu,
dhowells@...hat.com
Subject: Re: [PATCH tip/core/rcu 2/4] rcu: suppress RCU lockdep warnings
during early boot
On Thu, Mar 04, 2010 at 12:12:45PM +0100, Ingo Molnar wrote:
>
> * Paul E. McKenney <paulmck@...ux.vnet.ibm.com> wrote:
>
> > @@ -154,6 +167,10 @@ static inline int rcu_read_lock_sched_held(void)
> > # define rcu_read_acquire_sched() do { } while (0)
> > # define rcu_read_release_sched() do { } while (0)
> >
> > +static inline void debug_lockdep_rcu_update(void)
> > +{
> > +}
> > +
>
> Note, this method was only included for the !CONFIG_DEBUG_LOCK_ALLOC case, so
> i left it out for the time being.
>
> Which may result in a somewhat incomplete debug state, but it would at least
> build with lockdep enabled ;-)
Indeed, I clearly didn't test with the boot-time lock testing enabled. :-/
Please accept my apologies for my mess-up, and thank you for fixing it!
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