lkml.org 
[lkml]   [2005]   [Nov]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: 2.6.14-git3: scheduling while atomic from cpufreq on Athlon64
Date
On Sat, 5 Nov 2005 15:54:07 -0800, 
Ashok Raj <ashok.raj@intel.com> 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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-11-06 05:37    [W:0.117 / U:0.224 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site