On Wednesday, August 08, 2012, Colin Cross wrote:
> On Tue, Aug 7, 2012 at 3:15 PM, Rafael J. Wysocki wrote:
> > On Wednesday, July 25, 2012, Colin Cross wrote:
> >> The cpu hotplug notifier gets called in both atomic and non-atomic
> >> contexts, it is not always safe to lock a mutex. Filter
On Wednesday, August 08, 2012, Colin Cross wrote:
On Tue, Aug 7, 2012 at 3:15 PM, Rafael J. Wysocki r...@sisk.pl wrote:
On Wednesday, July 25, 2012, Colin Cross wrote:
The cpu hotplug notifier gets called in both atomic and non-atomic
contexts, it is not always safe to lock a mutex. Filter
On Tue, Aug 7, 2012 at 3:15 PM, Rafael J. Wysocki wrote:
> On Wednesday, July 25, 2012, Colin Cross wrote:
>> The cpu hotplug notifier gets called in both atomic and non-atomic
>> contexts, it is not always safe to lock a mutex. Filter out all events
>> except the six necessary ones, which are
On Wednesday, July 25, 2012, Colin Cross wrote:
> The cpu hotplug notifier gets called in both atomic and non-atomic
> contexts, it is not always safe to lock a mutex. Filter out all events
> except the six necessary ones, which are all sleepable, before taking
> the mutex.
>
> Signed-off-by:
On Wednesday, July 25, 2012, Colin Cross wrote:
The cpu hotplug notifier gets called in both atomic and non-atomic
contexts, it is not always safe to lock a mutex. Filter out all events
except the six necessary ones, which are all sleepable, before taking
the mutex.
Signed-off-by: Colin
On Tue, Aug 7, 2012 at 3:15 PM, Rafael J. Wysocki r...@sisk.pl wrote:
On Wednesday, July 25, 2012, Colin Cross wrote:
The cpu hotplug notifier gets called in both atomic and non-atomic
contexts, it is not always safe to lock a mutex. Filter out all events
except the six necessary ones, which
On 07/31/2012 11:57 PM, Colin Cross wrote:
> On Tue, Jul 31, 2012 at 8:43 AM, Srivatsa S. Bhat
> wrote:
>> On 07/26/2012 02:50 AM, Colin Cross wrote:
>>> The cpu hotplug notifier gets called in both atomic and non-atomic
>>> contexts, it is not always safe to lock a mutex. Filter out all events
On 07/31/2012 11:57 PM, Colin Cross wrote:
On Tue, Jul 31, 2012 at 8:43 AM, Srivatsa S. Bhat
srivatsa.b...@linux.vnet.ibm.com wrote:
On 07/26/2012 02:50 AM, Colin Cross wrote:
The cpu hotplug notifier gets called in both atomic and non-atomic
contexts, it is not always safe to lock a mutex.
On Tue, Jul 31, 2012 at 8:43 AM, Srivatsa S. Bhat
wrote:
> On 07/26/2012 02:50 AM, Colin Cross wrote:
>> The cpu hotplug notifier gets called in both atomic and non-atomic
>> contexts, it is not always safe to lock a mutex. Filter out all events
>> except the six necessary ones, which are all
On 07/26/2012 02:50 AM, Colin Cross wrote:
> The cpu hotplug notifier gets called in both atomic and non-atomic
> contexts, it is not always safe to lock a mutex. Filter out all events
> except the six necessary ones, which are all sleepable, before taking
> the mutex.
>
> Signed-off-by: Colin
On 07/26/2012 02:50 AM, Colin Cross wrote:
The cpu hotplug notifier gets called in both atomic and non-atomic
contexts, it is not always safe to lock a mutex. Filter out all events
except the six necessary ones, which are all sleepable, before taking
the mutex.
Signed-off-by: Colin Cross
On Tue, Jul 31, 2012 at 8:43 AM, Srivatsa S. Bhat
srivatsa.b...@linux.vnet.ibm.com wrote:
On 07/26/2012 02:50 AM, Colin Cross wrote:
The cpu hotplug notifier gets called in both atomic and non-atomic
contexts, it is not always safe to lock a mutex. Filter out all events
except the six
On Thu, Jul 26, 2012 at 9:25 AM, Shilimkar, Santosh
wrote:
> On Wed, Jul 25, 2012 at 11:20 PM, Colin Cross wrote:
>> The cpu hotplug notifier gets called in both atomic and non-atomic
>> contexts, it is not always safe to lock a mutex. Filter out all events
>> except the six necessary ones,
On Thursday, July 26, 2012, Rafael J. Wysocki wrote:
> On Thursday, July 26, 2012, Colin Cross wrote:
> > On Thu, Jul 26, 2012 at 12:55 PM, Rafael J. Wysocki wrote:
> > > On Wednesday, July 25, 2012, Colin Cross wrote:
> > >> The cpu hotplug notifier gets called in both atomic and non-atomic
> >
On Thursday, July 26, 2012, Colin Cross wrote:
> On Thu, Jul 26, 2012 at 12:55 PM, Rafael J. Wysocki wrote:
> > On Wednesday, July 25, 2012, Colin Cross wrote:
> >> The cpu hotplug notifier gets called in both atomic and non-atomic
> >> contexts, it is not always safe to lock a mutex. Filter out
On Thu, Jul 26, 2012 at 12:55 PM, Rafael J. Wysocki wrote:
> On Wednesday, July 25, 2012, Colin Cross wrote:
>> The cpu hotplug notifier gets called in both atomic and non-atomic
>> contexts, it is not always safe to lock a mutex. Filter out all events
>> except the six necessary ones, which are
On Wednesday, July 25, 2012, Colin Cross wrote:
> The cpu hotplug notifier gets called in both atomic and non-atomic
> contexts, it is not always safe to lock a mutex. Filter out all events
> except the six necessary ones, which are all sleepable, before taking
> the mutex.
I wonder what mutual
On Wed, Jul 25, 2012 at 11:20 PM, Colin Cross wrote:
> The cpu hotplug notifier gets called in both atomic and non-atomic
> contexts, it is not always safe to lock a mutex. Filter out all events
> except the six necessary ones, which are all sleepable, before taking
> the mutex.
>
>
On Wed, Jul 25, 2012 at 11:20 PM, Colin Cross ccr...@android.com wrote:
The cpu hotplug notifier gets called in both atomic and non-atomic
contexts, it is not always safe to lock a mutex. Filter out all events
except the six necessary ones, which are all sleepable, before taking
the mutex.
On Wednesday, July 25, 2012, Colin Cross wrote:
The cpu hotplug notifier gets called in both atomic and non-atomic
contexts, it is not always safe to lock a mutex. Filter out all events
except the six necessary ones, which are all sleepable, before taking
the mutex.
I wonder what mutual
On Thu, Jul 26, 2012 at 12:55 PM, Rafael J. Wysocki r...@sisk.pl wrote:
On Wednesday, July 25, 2012, Colin Cross wrote:
The cpu hotplug notifier gets called in both atomic and non-atomic
contexts, it is not always safe to lock a mutex. Filter out all events
except the six necessary ones,
On Thursday, July 26, 2012, Colin Cross wrote:
On Thu, Jul 26, 2012 at 12:55 PM, Rafael J. Wysocki r...@sisk.pl wrote:
On Wednesday, July 25, 2012, Colin Cross wrote:
The cpu hotplug notifier gets called in both atomic and non-atomic
contexts, it is not always safe to lock a mutex. Filter
On Thursday, July 26, 2012, Rafael J. Wysocki wrote:
On Thursday, July 26, 2012, Colin Cross wrote:
On Thu, Jul 26, 2012 at 12:55 PM, Rafael J. Wysocki r...@sisk.pl wrote:
On Wednesday, July 25, 2012, Colin Cross wrote:
The cpu hotplug notifier gets called in both atomic and non-atomic
On Thu, Jul 26, 2012 at 9:25 AM, Shilimkar, Santosh
santosh.shilim...@ti.com wrote:
On Wed, Jul 25, 2012 at 11:20 PM, Colin Cross ccr...@android.com wrote:
The cpu hotplug notifier gets called in both atomic and non-atomic
contexts, it is not always safe to lock a mutex. Filter out all events
The cpu hotplug notifier gets called in both atomic and non-atomic
contexts, it is not always safe to lock a mutex. Filter out all events
except the six necessary ones, which are all sleepable, before taking
the mutex.
Signed-off-by: Colin Cross
---
drivers/cpuidle/coupled.c | 12
The cpu hotplug notifier gets called in both atomic and non-atomic
contexts, it is not always safe to lock a mutex. Filter out all events
except the six necessary ones, which are all sleepable, before taking
the mutex.
Signed-off-by: Colin Cross ccr...@android.com
---
drivers/cpuidle/coupled.c
26 matches
Mail list logo
