From: khilman@ti•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [linux-pm] [PATCHv2 0/5] coupled cpuidle state support
Date: Mon, 09 Apr 2012 16:35:40 -0700 [thread overview]
Message-ID: <87mx6k7a2b.fsf@ti.com> (raw)
In-Reply-To: <4F828BAB.5010302@ti.com> (Santosh Shilimkar's message of "Mon, 09 Apr 2012 12:41:39 +0530")
Santosh Shilimkar <santosh.shilimkar@ti•com> writes:
> On Friday 30 March 2012 06:23 PM, Santosh Shilimkar wrote:
>> Colin,
>>
>> On Friday 16 March 2012 05:07 AM, Colin Cross wrote:
>>> On Wed, Mar 14, 2012 at 11:29 AM, Colin Cross <ccross@android•com> wrote:
>>
>> [...]
>>
>>>>
>>>> v2:
>>>> * removed the coupled lock, replacing it with atomic counters
>>>> * added a check for outstanding pokes before beginning the
>>>> final transition to avoid extra wakeups
>>>> * made the cpuidle_coupled struct completely private
>>>> * fixed kerneldoc comment formatting
>>>> * added a patch with a helper function for resynchronizing
>>>> cpus after aborting idle
>>>> * added a patch (not for merging) to add trace events for
>>>> verification and performance testing
>>>
>>> I forgot to mention, this patch series is on v3.3-rc7, and will
>>> conflict with the cpuidle timekeeping patches. If those go in first
>>> (which is likely), I will rework this series on top of it. I left it
>>> on v3.3-rc7 now to make testing easier.
>>
>> I have re-based your series against Len Browns
>> next branch [1] which has time keeping and other cpuidle patches.
>> Have also folded the CPU hotplug fix which I posted in the
>> original coupled idle patch.
>>
> As you know, we have been playing around this series for OMAP
> for last few weeks. This version series seems to work as intended
> and found it pretty stable in my testing. Apart from the cpu
> hotplug fix and the trace event comment, series looks fine
> to me.
>
> FWIW,
> Reviewed-by: Santosh Shilimkar <santosh.shilimkar@ti•com>
> Tested-by: Santosh Shilimkar <santosh.shilimkar@ti•com>
Also
Reviewed-by: Kevin Hilman <khilman@ti•com>
Tested-by: Kevin Hilman <khilman@ti•com>
as I've been working with Santosh on getting this stabilized on OMAP and
we are very keen to see this functionality merged.
Thanks,
Kevin
prev parent reply other threads:[~2012-04-09 23:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 18:29 [PATCHv2 0/5] coupled cpuidle state support Colin Cross
2012-03-14 18:29 ` [PATCHv2 1/5] cpuidle: refactor out cpuidle_enter_state Colin Cross
2012-03-14 18:29 ` [PATCHv2 2/5] cpuidle: fix error handling in __cpuidle_register_device Colin Cross
2012-03-14 18:29 ` [PATCHv2 3/5] cpuidle: add support for states that affect multiple cpus Colin Cross
2012-03-16 0:04 ` Kevin Hilman
2012-03-16 0:20 ` Colin Cross
2012-03-16 1:52 ` Arjan van de Ven
2012-03-17 12:29 ` Santosh Shilimkar
2012-03-17 19:21 ` Colin Cross
2012-03-18 7:18 ` Shilimkar, Santosh
2012-03-14 18:29 ` [PATCHv2 4/5] cpuidle: coupled: add parallel barrier function Colin Cross
2012-03-14 18:29 ` [PATCHv2 5/5] cpuidle: coupled: add trace events Colin Cross
2012-04-09 6:59 ` Santosh Shilimkar
2012-03-15 23:37 ` [PATCHv2 0/5] coupled cpuidle state support Colin Cross
2012-03-30 12:53 ` Santosh Shilimkar
2012-04-09 7:11 ` Santosh Shilimkar
2012-04-09 23:35 ` Kevin Hilman [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=87mx6k7a2b.fsf@ti.com \
--to=khilman@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox