Re: [PATCH Resend 1/3] sched: fix nr_busy_cpus with coupled cpuidle

From: Frederic Weisbecker
Date: Fri Jan 25 2013 - 08:00:41 EST


2013/1/25 Vincent Guittot <vincent.guittot@xxxxxxxxxx>:
> This sequence is not the right one
>
>> I'm going to look for the saved trace to check the sequence above
>
> I haven't been able to reproduce the bug that this patch was supposed to
> solved. The patch 2 and 3 seem enough to fix the nr_busy_cpus field. I will
> continue to try to reproduce it but it seems that it was a side effect of
> the 2 others fixes of the series

Ok. I just checked again as well and I can't find a scenario where
this can happen. If you find it out or trigger the bug again, don't
hesitate to resend this patch.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/