26 Sep
2013
26 Sep
'13
6:17 a.m.
On 26 September 2013 04:00, Daniel Lezcano daniel.lezcano@linaro.org wrote:
If you introduce a list, you will have to introduce a lock to protect it.
I missed it, should have added that :)
This lock will be in the fast path cpuidle_idle_call with the get_driver function and conforming to the comment: "NOTE: no locks or semaphores should be used here".
A lock has been introduced in this function already and the system hangs with 1024 cpus.
Hmm... I see.. I didn't knew about this expectation.. What about a rcu read/write lock? As far as I know its too lightweight... Can we have that in fast path?