From: Namhyung Kim <namhyung@kernel.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
tglx@linutronix.de
Subject: Re: [RFC 1/2] cpuidle: trace state of the CPU
Date: Thu, 31 Jan 2013 14:21:10 +0900 [thread overview]
Message-ID: <87y5faszax.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1359580757-4121-2-git-send-email-bigeasy@linutronix.de> (Sebastian Andrzej Siewior's message of "Wed, 30 Jan 2013 22:19:16 +0100")
On Wed, 30 Jan 2013 22:19:16 +0100, Sebastian Andrzej Siewior wrote:
> This patch adds an interface to cpuidle in order to retrieve the current
> idle state of a given CPU. Zero means the CPU is not in an idle state. Either
> because a cpuidle driver is not available or because the CPU is busy
> executing code. Values greater than zero the CPU indicate that the CPU
> is in some kind of idle state. The larger the value, the deeper the idle
> state.
>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
> drivers/cpuidle/cpuidle.c | 13 ++++++++++++-
> include/linux/cpuidle.h | 2 ++
> 2 files changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/cpuidle/cpuidle.c b/drivers/cpuidle/cpuidle.c
> index e1f6860..3594e0c 100644
> --- a/drivers/cpuidle/cpuidle.c
> +++ b/drivers/cpuidle/cpuidle.c
> @@ -23,6 +23,7 @@
> #include "cpuidle.h"
>
> DEFINE_PER_CPU(struct cpuidle_device *, cpuidle_devices);
> +static DEFINE_PER_CPU(unsigned int, cpu_state);
What about making it 'int' as cpuidle_get_state() returns int type?
>
> DEFINE_MUTEX(cpuidle_lock);
> LIST_HEAD(cpuidle_detected_devices);
> @@ -40,13 +41,23 @@ void disable_cpuidle(void)
> off = 1;
> }
>
> +int cpuidle_get_state(int cpu)
> +{
> + return per_cpu(cpu_state, cpu);
> +}
> +
> static int __cpuidle_register_device(struct cpuidle_device *dev);
>
> static inline int cpuidle_enter(struct cpuidle_device *dev,
> struct cpuidle_driver *drv, int index)
> {
> struct cpuidle_state *target_state = &drv->states[index];
> - return target_state->enter(dev, drv, index);
> + int ret;
> +
> + per_cpu(cpu_state, smp_processor_id()) = index + 1;
> + ret = target_state->enter(dev, drv, index);
> + per_cpu(cpu_state, smp_processor_id()) = 0;
Maybe we can use local variable 'cpu' for this duplicated
smp_processor_id() call as it's never executed on another cpu in
between?
Thanks,
Namhyung
> + return ret;
> }
>
> static inline int cpuidle_enter_tk(struct cpuidle_device *dev,
> diff --git a/include/linux/cpuidle.h b/include/linux/cpuidle.h
> index 24cd1037..256baeb 100644
> --- a/include/linux/cpuidle.h
> +++ b/include/linux/cpuidle.h
> @@ -155,6 +155,7 @@ extern int cpuidle_wrap_enter(struct cpuidle_device *dev,
> struct cpuidle_driver *drv, int index,
> int (*enter)(struct cpuidle_device *dev,
> struct cpuidle_driver *drv, int index));
> +extern int cpuidle_get_state(int cpu);
> extern int cpuidle_play_dead(void);
>
> extern struct cpuidle_driver *cpuidle_get_cpu_driver(struct cpuidle_device *dev);
> @@ -186,6 +187,7 @@ static inline int cpuidle_wrap_enter(struct cpuidle_device *dev,
> int (*enter)(struct cpuidle_device *dev,
> struct cpuidle_driver *drv, int index))
> { return -ENODEV; }
> +static inline int cpuidle_get_state(int cpu) {return 0; }
> static inline int cpuidle_play_dead(void) {return -ENODEV; }
> #endif
next prev parent reply other threads:[~2013-01-31 5:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 21:19 [RFC] Consider CPU idle state while choosing a new CPU Sebastian Andrzej Siewior
2013-01-30 21:19 ` [RFC 1/2] cpuidle: trace state of the CPU Sebastian Andrzej Siewior
2013-01-31 5:21 ` Namhyung Kim [this message]
2013-02-02 17:35 ` Sebastian Andrzej Siewior
2013-01-30 21:19 ` [RFC 2/2] sched/fair: prefer a CPU in the "lowest" idle state Sebastian Andrzej Siewior
2013-01-31 2:12 ` Michael Wang
2013-01-31 5:16 ` Namhyung Kim
2013-01-31 6:39 ` Michael Wang
2013-01-31 6:58 ` Namhyung Kim
2013-01-31 7:30 ` Michael Wang
2013-01-31 7:40 ` Namhyung Kim
2013-01-31 8:24 ` Michael Wang
2013-01-31 8:45 ` Michael Wang
2013-01-31 8:57 ` Michael Wang
2013-02-01 8:53 ` Namhyung Kim
2013-02-02 17:50 ` Sebastian Andrzej Siewior
2013-02-04 3:01 ` Michael Wang
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=87y5faszax.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=tglx@linutronix.de \
/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
Powered by JetHome