linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: deepthi@linux.vnet.ibm.com (Deepthi Dharwar)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH V6 0/4] cpuidle: Global registration of idle states with per-cpu statistics
Date: Fri, 23 Sep 2011 16:37:27 +0530	[thread overview]
Message-ID: <4E7C686F.30608@linux.vnet.ibm.com> (raw)
In-Reply-To: <87ty84tl7n.fsf@ti.com>

On Friday 23 September 2011 01:15 AM, Kevin Hilman wrote:
> Deepthi Dharwar <deepthi@linux.vnet.ibm.com> writes:
> 
>> The following patch series implements global registration of cpuidle
>> states, and also has the necessary data structure changes to
>> accommodate the per-cpu writable members of the cpuidle_states
>> structure.
> 
> I reviewed earlier versions of the series, and this version still looks
> good to me.  Any reason it is still RFC?
> 
> Reviewed-by: Kevin Hilman <khilman@ti.com>
> 
> and for the OMAP-specific parts,
> 
> Acked-by: Kevin Hilman <khilman@ti.com>
> 
> Kevin
> 
Hi Kevin,
Thanks for reviewing the patch.

This was posted as an RFC, as there were
a couple of ToDos listed in this patch series
which I thought needed additional review before 
I could ask for inclusion. 

To Do :
======

1. Russell King pointed out that in (V5 1/4) of this patch in
arch/arm/mach-at91/cpuidle.c, AT91 pieces may be broken.
In at91_enter_idle() routine, folks need to fix the two
consecutive asm() statements by combining
it to one as per the GCC reference manual.

Reference:
https://lkml.org/lkml/2011/6/6/273

2. In (V6 4/4), handle the case when idle states may change at run time
and acpi_processor_cst_has_changed() routine is called in a
better way than the current solution in this patch.

In this current solution where global registration is implemented,
the boot cpu on x86 would disable all the devices, repopulate the
states and later enable all the devices, irrespective of the cpu
that would receive the notification first.

Reference:
https://lkml.org/lkml/2011/4/25/83

Thanks & Regards,
 -Deepthi

      reply	other threads:[~2011-09-23 11:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-22  8:28 [RFC PATCH V6 0/4] cpuidle: Global registration of idle states with per-cpu statistics Deepthi Dharwar
2011-09-22  8:30 ` [RFC PATCH V6 1/4] cpuidle: Move dev->last_residency update to driver enter routine; remove dev->last_state Deepthi Dharwar
2011-09-22  8:31 ` [RFC PATCH V6 2/4] cpuidle: Remove CPUIDLE_FLAG_IGNORE and dev->prepare() Deepthi Dharwar
2011-09-22  8:32 ` [RFC PATCH V6 3/4] cpuidle: Split cpuidle_state structure and move per-cpu statistics fields Deepthi Dharwar
2011-09-22  8:34 ` [RFC PATCH V6 4/4] cpuidle: Single/Global registration of idle states Deepthi Dharwar
2011-09-22 17:35 ` [RFC PATCH V6 0/4] cpuidle: Global registration of idle states with per-cpu statistics Arjan van de Ven
2011-09-22 19:37 ` Jean Pihet
2011-09-22 19:45 ` Kevin Hilman
2011-09-23 11:07   ` Deepthi Dharwar [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=4E7C686F.30608@linux.vnet.ibm.com \
    --to=deepthi@linux.vnet.ibm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).