On 24/06/14 09:42, Chris Redpath wrote:
On 24/06/14 08:56, Alex Shi wrote:
On 06/23/2014 03:30 PM, Naresh Kamboju wrote:
To avoid the lock using, could we try per_cpu cpuidle driver?
Naresh, could you like to test this patch?
Sure Alex.
I will test and post you results.
Hi, Naresh, did you test this patch?
Tixy, Chris,
Any comments for this idea?
Hi Alex,
I've had a look at the patch, I'm not sure if it will make any difference as the potential deadlock is on the same CPU.
I will try to have a better look at it this morning.
--Chris
Hi Alex,
I've had a better look - the per-cpu driver interface doesn't use locking at all so any potential deadlock will of course not occur.
The reason I used cpuidle_driver_ref was to ensure that driver data did not go away while I was reading it, as there isn't any notification for driver changes.
Is it possible to change the cpuidle driver after it has been setup? I didn't find anything which said it was not allowed.
--Chris
linaro-kernel mailing list linaro-kernel@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-kernel