Re: [PATCH 2/3] cpuidle: coupled: abort idle if pokes are pending

2013-08-26 Thread Joseph Lo
On Sat, 2013-08-24 at 03:45 +0800, Colin Cross wrote: > Joseph Lo reported a lockup on Tegra3 caused > by a race condition in coupled cpuidle. When two or more cpus Actually this issue can be reproduced on both Tegra20/30 platforms. And I suggest using Tegra20 to replace Tegra3 here, we only

Re: [PATCH 2/3] cpuidle: coupled: abort idle if pokes are pending

2013-08-26 Thread Joseph Lo
On Sat, 2013-08-24 at 03:45 +0800, Colin Cross wrote: Joseph Lo jose...@nvidia.com reported a lockup on Tegra3 caused by a race condition in coupled cpuidle. When two or more cpus Actually this issue can be reproduced on both Tegra20/30 platforms. And I suggest using Tegra20 to replace Tegra3

[PATCH 2/3] cpuidle: coupled: abort idle if pokes are pending

2013-08-23 Thread Colin Cross
Joseph Lo reported a lockup on Tegra3 caused by a race condition in coupled cpuidle. When two or more cpus enter idle at the same time, the first cpus to arrive may go to the ready loop without processing pending pokes from the last cpu to arrive. This patch adds a check for pending pokes once

[PATCH 2/3] cpuidle: coupled: abort idle if pokes are pending

2013-08-23 Thread Colin Cross
Joseph Lo jose...@nvidia.com reported a lockup on Tegra3 caused by a race condition in coupled cpuidle. When two or more cpus enter idle at the same time, the first cpus to arrive may go to the ready loop without processing pending pokes from the last cpu to arrive. This patch adds a check for