Re: 2.6.14-git3: scheduling while atomic from cpufreq on Athlon64

[Keith Owens]

On Sat, 5 Nov 2005 15:54:07 -0800, 
Ashok Raj <ashok.raj@xxxxxxxxx> wrote:
>Since when we already in the cpu notifier callbacks, cpucontrol is already
>held by the cpu_up() or the cpu_down() that caused the double lock.

Add the owning cpu id to the lock.  spin_trylock() first, if the lock
is already held then check if the current cpu owns the lock.  If it
does then continue, noting (in a local variable) that you do not need
to drop the lock on exit from this recursion level.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/