[lkml]   [2006]   [Jul]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.6.18-rc1-mm1
> > - If a piece of kernel code is dealing with per-cpu data and cannot run
> > atomically then it should have its own cpu hotplug handlers anyway. It
> > is up to that code (ie: cpufreq) to provide its own locking against its
> > own CPU hotplug callback.
> This still does not solve this cpufreq problem where it is trying to
> take the same lock twice down the same call path.

that is broken beyond discussing anyway... "we don't know our locking
rules so we do recursive mutexes" is ... NOT a good reason.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-07-10 10:53    [W:0.065 / U:13.016 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site