[ ... ]
The following patch is a hot fix by returning to the initial behavior
by removing the lock when getting the driver.
>>>
>>> The patch fixes the problem. Verified on a system with 1024 cpus.
>>> Thanks.
>>>
Signed-off-by: Daniel Lezcano
>>>
>>> Reported-by: Russ Anderson
[ ... ]
The following patch is a hot fix by returning to the initial behavior
by removing the lock when getting the driver.
The patch fixes the problem. Verified on a system with 1024 cpus.
Thanks.
Signed-off-by: Daniel Lezcano daniel.lezc...@linaro.org
Reported-by: Russ Anderson
On Friday, January 04, 2013 07:27:24 AM Daniel Lezcano wrote:
> On 01/02/2013 10:13 PM, Russ Anderson wrote:
> > On Wed, Dec 26, 2012 at 11:01:48AM +0100, Daniel Lezcano wrote:
> >> The commit bf4d1b5ddb78f86078ac6ae0415802d5f0c68f92 introduces
> >> a lock in the cpuidle_get_cpu_driver function.
On Friday, January 04, 2013 07:27:24 AM Daniel Lezcano wrote:
On 01/02/2013 10:13 PM, Russ Anderson wrote:
On Wed, Dec 26, 2012 at 11:01:48AM +0100, Daniel Lezcano wrote:
The commit bf4d1b5ddb78f86078ac6ae0415802d5f0c68f92 introduces
a lock in the cpuidle_get_cpu_driver function. This
On 01/02/2013 10:13 PM, Russ Anderson wrote:
> On Wed, Dec 26, 2012 at 11:01:48AM +0100, Daniel Lezcano wrote:
>> The commit bf4d1b5ddb78f86078ac6ae0415802d5f0c68f92 introduces
>> a lock in the cpuidle_get_cpu_driver function. This function
>> is used in the idle_call function.
>>
>> The problem
On 01/02/2013 10:13 PM, Russ Anderson wrote:
On Wed, Dec 26, 2012 at 11:01:48AM +0100, Daniel Lezcano wrote:
The commit bf4d1b5ddb78f86078ac6ae0415802d5f0c68f92 introduces
a lock in the cpuidle_get_cpu_driver function. This function
is used in the idle_call function.
The problem is the
On Wed, Dec 26, 2012 at 11:01:48AM +0100, Daniel Lezcano wrote:
> The commit bf4d1b5ddb78f86078ac6ae0415802d5f0c68f92 introduces
> a lock in the cpuidle_get_cpu_driver function. This function
> is used in the idle_call function.
>
> The problem is the contention with a large number of cpus
On Wed, Dec 26, 2012 at 11:01:48AM +0100, Daniel Lezcano wrote:
The commit bf4d1b5ddb78f86078ac6ae0415802d5f0c68f92 introduces
a lock in the cpuidle_get_cpu_driver function. This function
is used in the idle_call function.
The problem is the contention with a large number of cpus because
On Sat, Dec 29, 2012 at 11:03:03AM +0100, Daniel Lezcano wrote:
>
> Hi Russ,
>
> Is it possible you try this patch on your 2048 cpus ?
Yes, I will try it later today.
Thanks
> Thanks
>
> -- Daniel
>
> On 12/26/2012 11:01 AM, Daniel Lezcano wrote:
> > The commit
On Sat, Dec 29, 2012 at 11:03:03AM +0100, Daniel Lezcano wrote:
Hi Russ,
Is it possible you try this patch on your 2048 cpus ?
Yes, I will try it later today.
Thanks
Thanks
-- Daniel
On 12/26/2012 11:01 AM, Daniel Lezcano wrote:
The commit
Hi Russ,
Is it possible you try this patch on your 2048 cpus ?
Thanks
-- Daniel
On 12/26/2012 11:01 AM, Daniel Lezcano wrote:
> The commit bf4d1b5ddb78f86078ac6ae0415802d5f0c68f92 introduces
> a lock in the cpuidle_get_cpu_driver function. This function
> is used in the idle_call function.
Hi Russ,
Is it possible you try this patch on your 2048 cpus ?
Thanks
-- Daniel
On 12/26/2012 11:01 AM, Daniel Lezcano wrote:
The commit bf4d1b5ddb78f86078ac6ae0415802d5f0c68f92 introduces
a lock in the cpuidle_get_cpu_driver function. This function
is used in the idle_call function.
The commit bf4d1b5ddb78f86078ac6ae0415802d5f0c68f92 introduces
a lock in the cpuidle_get_cpu_driver function. This function
is used in the idle_call function.
The problem is the contention with a large number of cpus because
they try to access the idle routine at the same time.
The lock could be
The commit bf4d1b5ddb78f86078ac6ae0415802d5f0c68f92 introduces
a lock in the cpuidle_get_cpu_driver function. This function
is used in the idle_call function.
The problem is the contention with a large number of cpus because
they try to access the idle routine at the same time.
The lock could be
14 matches
Mail list logo