From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Russ Anderson <rja@sgi.com>,
linux-pm@vger.kernel.org, pdeschrijver@nvidia.com,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
rja@americas.sgi.com
Subject: Re: [PATCH] cpuidle - fix lock contention in the idle path
Date: Mon, 07 Jan 2013 00:07:00 +0100 [thread overview]
Message-ID: <50EA0394.9020701@linaro.org> (raw)
In-Reply-To: <3077900.eue4T2ZoF8@vostro.rjw.lan>
[ ... ]
>>>> 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.lezcano@linaro.org>
>>>
>>> Reported-by: Russ Anderson <rja@sgi.com>
>>> Acked-by: Russ Anderson <rja@sgi.com>
>>
>> Hi Rafael,
>>
>> could you consider this patch for merging ?
>
> Yes, I've taken it already.
>
> I'll include it into the next pull request.
Ok, thanks.
I noticed you rephrased the changelog. Thanks for that also.
-- Daniel
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
* English - detected
* English
* French
* English
* French
<javascript:void(0);> <#>
prev parent reply other threads:[~2013-01-06 23:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-26 10:01 [PATCH] cpuidle - fix lock contention in the idle path Daniel Lezcano
2012-12-29 10:03 ` Daniel Lezcano
2012-12-31 15:08 ` Russ Anderson
2013-01-02 21:13 ` Russ Anderson
2013-01-04 6:27 ` Daniel Lezcano
2013-01-05 0:03 ` Rafael J. Wysocki
2013-01-06 23:07 ` Daniel Lezcano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50EA0394.9020701@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pdeschrijver@nvidia.com \
--cc=rja@americas.sgi.com \
--cc=rja@sgi.com \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.