lkml.org 
[lkml]   [2006]   [May]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [patch 00/61] ANNOUNCE: lock validator -V1
    From
    Date
    On Tue, 2006-05-30 at 10:10 -0400, Dave Jones wrote:
    > On Tue, May 30, 2006 at 07:45:47AM +0200, Arjan van de Ven wrote:
    >
    > > One
    > > ---
    > > store_scaling_governor takes policy->lock and then calls __cpufreq_set_policy
    > > __cpufreq_set_policy calls __cpufreq_governor
    > > __cpufreq_governor calls __cpufreq_driver_target via cpufreq_governor_performance
    > > __cpufreq_driver_target calls lock_cpu_hotplug() (which takes the hotplug lock)
    > >
    > >
    > > Two
    > > ---
    > > cpufreq_stats_init lock_cpu_hotplug() and then calls cpufreq_stat_cpu_callback
    > > cpufreq_stat_cpu_callback calls cpufreq_update_policy
    > > cpufreq_update_policy takes the policy->lock
    > >
    > >
    > > so this looks like a real honest AB-BA deadlock to me...
    >
    > This looks a little clearer this morning. I missed the fact that sys_init_module
    > isn't completely serialised, only the loading part. ->init routines can and will be
    > called in parallel.
    >
    > I don't see where cpufreq_update_policy takes policy->lock though.
    > In my tree it just takes the per-cpu data->lock.

    isn't that basically the same lock?


    -
    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: 2006-05-30 16:21    [W:0.041 / U:184.516 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site