All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: lenb@kernel.org, linux-pm@vger.kernel.org, patches@linaro.org,
	linaro-kernel@lists.linaro.org
Subject: Re: [PATCH 1/2] cpuidle: add hotplug support to initialize the timer broadcast
Date: Tue, 06 Aug 2013 16:11:20 +0200	[thread overview]
Message-ID: <52010408.2000703@linaro.org> (raw)
In-Reply-To: <3064063.5AHNzeThpF@vostro.rjw.lan>

On 08/06/2013 04:10 PM, Rafael J. Wysocki wrote:
> On Tuesday, August 06, 2013 10:36:21 AM Daniel Lezcano wrote:
>> On 07/30/2013 03:54 PM, Daniel Lezcano wrote:
>>> Commit 89878baa73f0f1c679355006bd8632e5d78f96c2 introduced the flag
>>> CPUIDLE_FLAG_TIMER_STOP where we specify a specific idle state stops the local
>>> timer.
>>>
>>> Commit a06df062a189a8d5588babb8bf0bb78672497798 introduced the initialization
>>> of the timer broadcast framework depending of the flag presence.
>>>
>>> If a system is booted with some cpus offline, by setting for example, maxcpus=1
>>> in the kernel command line, and then they are set online, the timer broadcast
>>> won't be setup automatically.
>>>
>>> Fix this by adding the cpu hotplug notifier and enable/disable the timer
>>> broadcast automatically. So no need to handle that at the arch specific driver
>>> level like eg. intel_idle does.
>>>
>>> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
>>> ---
>>
>> Len, Rafael,
>>
>> any comment on these two patches ?
> 
> Honestly, I didn't have the time to look into that and Len is on vacation.
> 
> It's on my todo list, however.

Ah, ok. Thanks.

  -- Daniel


>>>  drivers/cpuidle/driver.c |   48 ++++++++++++++++++++++++++++++++++++++++++++++
>>>  1 file changed, 48 insertions(+)
>>>
>>> diff --git a/drivers/cpuidle/driver.c b/drivers/cpuidle/driver.c
>>> index 3ac499d..e976994 100644
>>> --- a/drivers/cpuidle/driver.c
>>> +++ b/drivers/cpuidle/driver.c
>>> @@ -10,6 +10,7 @@
>>>  
>>>  #include <linux/mutex.h>
>>>  #include <linux/module.h>
>>> +#include <linux/cpu.h>
>>>  #include <linux/cpuidle.h>
>>>  #include <linux/cpumask.h>
>>>  #include <linux/clockchips.h>
>>> @@ -147,6 +148,48 @@ static void cpuidle_setup_broadcast_timer(void *arg)
>>>  }
>>>  
>>>  /**
>>> + * cpuidle_hotplug_notify: notifier callback when a cpu is onlined/offlined
>>> + * @n: the notifier block
>>> + * @action: an unsigned long giving the event related to the notification
>>> + * @hcpu: a void pointer but used as the cpu number which the event is related
>>> + *
>>> + * The kernel can boot with some cpus offline, we have to init the timer
>>> + * broadcast for these cpus when they are onlined. Also we have to disable
>>> + * the timer broadcast when the cpu is down.
>>> + *
>>> + * Returns NOTIFY_OK
>>> + */
>>> +static int cpuidle_hotplug_notify(struct notifier_block *n,
>>> +				  unsigned long action, void *hcpu)
>>> +{
>>> +	int cpu = (unsigned long)hcpu;
>>> +	struct cpuidle_driver *drv;
>>> +
>>> +	drv = __cpuidle_get_cpu_driver(cpu);
>>> +	if (!drv || !drv->bctimer)
>>> +		goto out;
>>> +
>>> +	switch (action & 0xf) {
>>> +	case CPU_ONLINE:
>>> +		smp_call_function_single(cpu, cpuidle_setup_broadcast_timer,
>>> +					 (void *)CLOCK_EVT_NOTIFY_BROADCAST_ON,
>>> +					 1);
>>> +		break;
>>> +	case CPU_DEAD:
>>> +		smp_call_function_single(cpu, cpuidle_setup_broadcast_timer,
>>> +					 (void *)CLOCK_EVT_NOTIFY_BROADCAST_OFF,
>>> +					 1);
>>> +		break;
>>> +	}
>>> +out:
>>> +	return NOTIFY_OK;
>>> +}
>>> +
>>> +static struct notifier_block cpuidle_hotplug_notifier = {
>>> +	.notifier_call = cpuidle_hotplug_notify,
>>> +};
>>> +
>>> +/**
>>>   * __cpuidle_driver_init - initialize the driver's internal data
>>>   * @drv: a valid pointer to a struct cpuidle_driver
>>>   *
>>> @@ -262,6 +305,9 @@ int cpuidle_register_driver(struct cpuidle_driver *drv)
>>>  	ret = __cpuidle_register_driver(drv);
>>>  	spin_unlock(&cpuidle_driver_lock);
>>>  
>>> +	if (!ret)
>>> +		ret = register_cpu_notifier(&cpuidle_hotplug_notifier);
>>> +
>>>  	return ret;
>>>  }
>>>  EXPORT_SYMBOL_GPL(cpuidle_register_driver);
>>> @@ -276,6 +322,8 @@ EXPORT_SYMBOL_GPL(cpuidle_register_driver);
>>>   */
>>>  void cpuidle_unregister_driver(struct cpuidle_driver *drv)
>>>  {
>>> +	unregister_cpu_notifier(&cpuidle_hotplug_notifier);
>>> +
>>>  	spin_lock(&cpuidle_driver_lock);
>>>  	__cpuidle_unregister_driver(drv);
>>>  	spin_unlock(&cpuidle_driver_lock);
>>>
>>
>>
>>


-- 
 <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


  reply	other threads:[~2013-08-06 14:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30 13:54 [PATCH 1/2] cpuidle: add hotplug support to initialize the timer broadcast Daniel Lezcano
2013-07-30 13:54 ` [PATCH 2/2] x86: cpuidle: remove broadcast timer initialization Daniel Lezcano
2013-08-20 14:11   ` Rafael J. Wysocki
2013-09-02 14:02     ` Daniel Lezcano
2013-08-06  8:36 ` [PATCH 1/2] cpuidle: add hotplug support to initialize the timer broadcast Daniel Lezcano
2013-08-06 14:10   ` Rafael J. Wysocki
2013-08-06 14:11     ` Daniel Lezcano [this message]
2013-08-20 14:07 ` Rafael J. Wysocki
2013-09-02 13:29   ` Daniel Lezcano

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=52010408.2000703@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=lenb@kernel.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=patches@linaro.org \
    --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.