ers@vger.kernel.org; Ingo Molnar; r...@sisk.pl; Dave
> > > >Young; Pekka Enberg
> > > >Cc: Mathieu Desnoyers; Li, Shaohua; Rusty Russell;
> > > >sven.wege...@stealer.net
> > > >Subject: [patch 2.6.30 3/4] cpufreq add gov mutex
> >
hieu Desnoyers; Li, Shaohua; Rusty Russell;
> > >sven.wege...@stealer.net
> > >Subject: [patch 2.6.30 3/4] cpufreq add gov mutex
> > >
> > >Using the cpufreq_gov_mutex to protect internal governor data
> > >structures. The
> > >policy rwsem write lo
ve
> >Jones; Thomas Renninger; cpuf...@vger.kernel.org;
> >kernel-testers@vger.kernel.org; Ingo Molnar; r...@sisk.pl; Dave
> >Young; Pekka Enberg
> >Cc: Mathieu Desnoyers; Li, Shaohua; Rusty Russell;
> >sven.wege...@stealer.net
> >Subject: [patch 2.6.30 3/4] c
rg; Ingo Molnar; r...@sisk.pl; Dave
>Young; Pekka Enberg
>Cc: Mathieu Desnoyers; Li, Shaohua; Rusty Russell;
>sven.wege...@stealer.net
>Subject: [patch 2.6.30 3/4] cpufreq add gov mutex
>
>Using the cpufreq_gov_mutex to protect internal governor data
>structures. The
>polic
Using the cpufreq_gov_mutex to protect internal governor data structures. The
policy rwsem write lock nests inside this mutex. The policy rwsem is taken in
the timer handler, and therefore cannot be held while doing a sync teardown of
the timer. This cpufreq_gov_mutex lock protects init/teardown
