2013/1/25 Vincent Guittot :
>
> Le 25 janv. 2013 13:00, "Frederic Weisbecker" a écrit :
>
>
>>
>> 2013/1/25 Vincent Guittot :
>> > 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
2013/1/25 Vincent Guittot :
> 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
>
2013/1/25 Vincent Guittot vincent.guit...@linaro.org:
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
2013/1/25 Vincent Guittot vincent.guit...@linaro.org:
Le 25 janv. 2013 13:00, Frederic Weisbecker fweis...@gmail.com a écrit :
2013/1/25 Vincent Guittot vincent.guit...@linaro.org:
This sequence is not the right one
I'm going to look for the saved trace to check the sequence above
On 24 January 2013 17:44, Frederic Weisbecker wrote:
> 2012/12/3 Vincent Guittot :
>> With the coupled cpuidle driver (but probably also with other drivers),
>> a CPU loops in a temporary safe state while waiting for other CPUs of its
>> cluster to be ready to enter the coupled C-state. If an IRQ
2012/12/3 Vincent Guittot :
> With the coupled cpuidle driver (but probably also with other drivers),
> a CPU loops in a temporary safe state while waiting for other CPUs of its
> cluster to be ready to enter the coupled C-state. If an IRQ or a softirq
> occurs, the CPU will stay in this internal
2012/12/3 Vincent Guittot vincent.guit...@linaro.org:
With the coupled cpuidle driver (but probably also with other drivers),
a CPU loops in a temporary safe state while waiting for other CPUs of its
cluster to be ready to enter the coupled C-state. If an IRQ or a softirq
occurs, the CPU will
On 24 January 2013 17:44, Frederic Weisbecker fweis...@gmail.com wrote:
2012/12/3 Vincent Guittot vincent.guit...@linaro.org:
With the coupled cpuidle driver (but probably also with other drivers),
a CPU loops in a temporary safe state while waiting for other CPUs of its
cluster to be ready to
With the coupled cpuidle driver (but probably also with other drivers),
a CPU loops in a temporary safe state while waiting for other CPUs of its
cluster to be ready to enter the coupled C-state. If an IRQ or a softirq
occurs, the CPU will stay in this internal loop if there is no need
to resched.
With the coupled cpuidle driver (but probably also with other drivers),
a CPU loops in a temporary safe state while waiting for other CPUs of its
cluster to be ready to enter the coupled C-state. If an IRQ or a softirq
occurs, the CPU will stay in this internal loop if there is no need
to resched.
10 matches
Mail list logo