On 13-02-04 05:48 AM, Thomas Gleixner wrote:
On Fri, 25 Jan 2013, Paul Gortmaker wrote:
From: Thomas Gleixner t...@linutronix.de
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 :(
On 01/25/2013 12:21 PM, Paul Gortmaker wrote:
From: Thomas Gleixner t...@linutronix.de
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
From: Thomas Gleixner t...@linutronix.de
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
