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

2013-01-25 Thread Frederic Weisbecker
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

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

2013-01-25 Thread Frederic Weisbecker
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 >

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

2013-01-25 Thread Frederic Weisbecker
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

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

2013-01-25 Thread Frederic Weisbecker
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

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

2013-01-24 Thread Vincent Guittot
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

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

2013-01-24 Thread Frederic Weisbecker
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

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

2013-01-24 Thread Frederic Weisbecker
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

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

2013-01-24 Thread Vincent Guittot
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

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

2012-12-03 Thread 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 loop if there is no need to resched.

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

2012-12-03 Thread 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 loop if there is no need to resched.