On 26 September 2013 04:00, Daniel Lezcano <daniel.lezc...@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? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
