On Fri, 25 Jan 2013, Paul Gortmaker wrote: > From: Thomas Gleixner <tglx@xxxxxxxxxxxxx> > > There is no real reason to use a rwlock for devtree_lock. It even > could be a mutex, but unfortunately it's locked from cpu hotplug > paths which can't schedule :( > > So it needs to become a raw lock on rt as well. The devtree_lock would > be the only user of a raw_rw_lock, so we are better off cleaning up the > recursive locking paths which allows us to convert devtree_lock to a > read_lock. Hmm. It's already a rw_lock. For RT we want to change that thing to a raw_spinlock. Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
