From: Lina Iyer <lina.iyer@linaro.org> To: ulf.hansson@linaro.org, khilman@kernel.org, rjw@rjwysocki.net, linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org Cc: geert@linux-m68k.org, k.kozlowski@samsung.com, msivasub@codeaurora.org, agross@codeaurora.org, sboyd@codeaurora.org, linux-arm-msm@vger.kernel.org, lorenzo.pieralisi@arm.com, ahaslam@baylibre.com, mtitinger@baylibre.com, Lina Iyer <lina.iyer@linaro.org>, Thomas Gleixner <tglx@linutronix.de> Subject: [RFC v2 05/12] timer: Export next wake up of a CPU Date: Fri, 12 Feb 2016 13:50:31 -0700 [thread overview] Message-ID: <1455310238-8963-6-git-send-email-lina.iyer@linaro.org> (raw) In-Reply-To: <1455310238-8963-1-git-send-email-lina.iyer@linaro.org> Knowing the sleep length of the CPU is useful for the power state determination on idle. However, when the common sleep time between multiple CPUs is needed, the sleep length of a CPU is not useful. By reading the next wake up event of a CPU, governors can determine the first CPU to wake up (due to timer) amongst a cluster of CPUs and the sleep time available between the last CPU to idle and the first CPU to resume. This information is useful to determine if the caches and other common hardware blocks can also be put in idle during this common period of inactivity. Cc: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Lina Iyer <lina.iyer@linaro.org> --- Changes since RFC v1 - - any CPU can access this variable if that CPU has IRQs disabled include/linux/tick.h | 10 ++++++++++ kernel/time/tick-sched.c | 13 +++++++++++++ 2 files changed, 23 insertions(+) diff --git a/include/linux/tick.h b/include/linux/tick.h index 97fd4e5..b8a2e06 100644 --- a/include/linux/tick.h +++ b/include/linux/tick.h @@ -104,6 +104,7 @@ extern void tick_nohz_idle_enter(void); extern void tick_nohz_idle_exit(void); extern void tick_nohz_irq_exit(void); extern ktime_t tick_nohz_get_sleep_length(void); +extern ktime_t tick_nohz_get_next_wakeup(int cpu); extern u64 get_cpu_idle_time_us(int cpu, u64 *last_update_time); extern u64 get_cpu_iowait_time_us(int cpu, u64 *last_update_time); #else /* !CONFIG_NO_HZ_COMMON */ @@ -118,6 +119,15 @@ static inline ktime_t tick_nohz_get_sleep_length(void) return len; } + +static inline ktime_t tick_nohz_get_next_wakeup(int cpu) +{ + ktime_t len = { .tv64 = NSEC_PER_SEC/HZ }; + + /* Next wake up is the tick period, assume it starts now */ + return ktime_add(len, ktime_get()); +} + static inline u64 get_cpu_idle_time_us(int cpu, u64 *unused) { return -1; } static inline u64 get_cpu_iowait_time_us(int cpu, u64 *unused) { return -1; } #endif /* !CONFIG_NO_HZ_COMMON */ diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c index 0b17424..f0ddaec 100644 --- a/kernel/time/tick-sched.c +++ b/kernel/time/tick-sched.c @@ -888,6 +888,19 @@ ktime_t tick_nohz_get_sleep_length(void) return ts->sleep_length; } +/** + * tick_nohz_get_next_wakeup - return the next wake up of the CPU + * + * Called with interrupts disabled on the cpu + */ +ktime_t tick_nohz_get_next_wakeup(int cpu) +{ + struct clock_event_device *dev = + per_cpu(tick_cpu_device.evtdev, cpu); + + return dev->next_event; +} + static void tick_nohz_account_idle_ticks(struct tick_sched *ts) { #ifndef CONFIG_VIRT_CPU_ACCOUNTING_NATIVE -- 2.1.4
WARNING: multiple messages have this Message-ID (diff)
From: lina.iyer@linaro.org (Lina Iyer) To: linux-arm-kernel@lists.infradead.org Subject: [RFC v2 05/12] timer: Export next wake up of a CPU Date: Fri, 12 Feb 2016 13:50:31 -0700 [thread overview] Message-ID: <1455310238-8963-6-git-send-email-lina.iyer@linaro.org> (raw) In-Reply-To: <1455310238-8963-1-git-send-email-lina.iyer@linaro.org> Knowing the sleep length of the CPU is useful for the power state determination on idle. However, when the common sleep time between multiple CPUs is needed, the sleep length of a CPU is not useful. By reading the next wake up event of a CPU, governors can determine the first CPU to wake up (due to timer) amongst a cluster of CPUs and the sleep time available between the last CPU to idle and the first CPU to resume. This information is useful to determine if the caches and other common hardware blocks can also be put in idle during this common period of inactivity. Cc: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Lina Iyer <lina.iyer@linaro.org> --- Changes since RFC v1 - - any CPU can access this variable if that CPU has IRQs disabled include/linux/tick.h | 10 ++++++++++ kernel/time/tick-sched.c | 13 +++++++++++++ 2 files changed, 23 insertions(+) diff --git a/include/linux/tick.h b/include/linux/tick.h index 97fd4e5..b8a2e06 100644 --- a/include/linux/tick.h +++ b/include/linux/tick.h @@ -104,6 +104,7 @@ extern void tick_nohz_idle_enter(void); extern void tick_nohz_idle_exit(void); extern void tick_nohz_irq_exit(void); extern ktime_t tick_nohz_get_sleep_length(void); +extern ktime_t tick_nohz_get_next_wakeup(int cpu); extern u64 get_cpu_idle_time_us(int cpu, u64 *last_update_time); extern u64 get_cpu_iowait_time_us(int cpu, u64 *last_update_time); #else /* !CONFIG_NO_HZ_COMMON */ @@ -118,6 +119,15 @@ static inline ktime_t tick_nohz_get_sleep_length(void) return len; } + +static inline ktime_t tick_nohz_get_next_wakeup(int cpu) +{ + ktime_t len = { .tv64 = NSEC_PER_SEC/HZ }; + + /* Next wake up is the tick period, assume it starts now */ + return ktime_add(len, ktime_get()); +} + static inline u64 get_cpu_idle_time_us(int cpu, u64 *unused) { return -1; } static inline u64 get_cpu_iowait_time_us(int cpu, u64 *unused) { return -1; } #endif /* !CONFIG_NO_HZ_COMMON */ diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c index 0b17424..f0ddaec 100644 --- a/kernel/time/tick-sched.c +++ b/kernel/time/tick-sched.c @@ -888,6 +888,19 @@ ktime_t tick_nohz_get_sleep_length(void) return ts->sleep_length; } +/** + * tick_nohz_get_next_wakeup - return the next wake up of the CPU + * + * Called with interrupts disabled on the cpu + */ +ktime_t tick_nohz_get_next_wakeup(int cpu) +{ + struct clock_event_device *dev = + per_cpu(tick_cpu_device.evtdev, cpu); + + return dev->next_event; +} + static void tick_nohz_account_idle_ticks(struct tick_sched *ts) { #ifndef CONFIG_VIRT_CPU_ACCOUNTING_NATIVE -- 2.1.4
next prev parent reply other threads:[~2016-02-12 20:50 UTC|newest] Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-02-12 20:50 [RFC v2 00/12] PM: SoC idle support using PM domains Lina Iyer 2016-02-12 20:50 ` Lina Iyer 2016-02-12 20:50 ` [RFC v2 01/12] PM / Domains: Abstract genpd locking Lina Iyer 2016-02-12 20:50 ` Lina Iyer 2016-02-26 18:08 ` Stephen Boyd 2016-02-26 18:08 ` Stephen Boyd 2016-03-01 16:55 ` Lina Iyer 2016-03-01 16:55 ` Lina Iyer 2016-02-12 20:50 ` [RFC v2 02/12] PM / Domains: Support IRQ safe PM domains Lina Iyer 2016-02-12 20:50 ` Lina Iyer 2016-02-26 18:17 ` Stephen Boyd 2016-02-26 18:17 ` Stephen Boyd 2016-03-01 17:44 ` Lina Iyer 2016-03-01 17:44 ` Lina Iyer 2016-02-12 20:50 ` [RFC v2 03/12] PM / cpu_domains: Setup PM domains for CPUs/clusters Lina Iyer 2016-02-12 20:50 ` Lina Iyer 2016-02-17 23:38 ` Lina Iyer 2016-02-17 23:38 ` Lina Iyer 2016-02-18 17:29 ` [BUG FIX] PM / cpu_domains: Check for NULL callbacks Lina Iyer 2016-02-18 17:29 ` Lina Iyer 2016-02-18 17:46 ` Rafael J. Wysocki 2016-02-18 17:46 ` Rafael J. Wysocki 2016-02-18 22:51 ` Lina Iyer 2016-02-18 22:51 ` Lina Iyer 2016-02-26 19:10 ` [RFC v2 03/12] PM / cpu_domains: Setup PM domains for CPUs/clusters Stephen Boyd 2016-02-26 19:10 ` Stephen Boyd 2016-03-01 18:00 ` Lina Iyer 2016-03-01 18:00 ` Lina Iyer 2016-02-12 20:50 ` [RFC v2 04/12] ARM: cpuidle: Add runtime PM support for CPUs Lina Iyer 2016-02-12 20:50 ` Lina Iyer 2016-02-26 18:24 ` Stephen Boyd 2016-02-26 18:24 ` Stephen Boyd 2016-03-01 18:36 ` Lina Iyer 2016-03-01 18:36 ` Lina Iyer 2016-02-12 20:50 ` Lina Iyer [this message] 2016-02-12 20:50 ` [RFC v2 05/12] timer: Export next wake up of a CPU Lina Iyer 2016-02-12 20:50 ` [RFC v2 06/12] PM / cpu_domains: Record CPUs that are part of the domain Lina Iyer 2016-02-12 20:50 ` Lina Iyer 2016-02-26 19:20 ` Stephen Boyd 2016-02-26 19:20 ` Stephen Boyd 2016-03-01 19:24 ` Lina Iyer 2016-03-01 19:24 ` Lina Iyer 2016-02-12 20:50 ` [RFC v2 07/12] PM / cpu_domains: Add PM Domain governor for CPUs Lina Iyer 2016-02-12 20:50 ` Lina Iyer 2016-02-26 19:33 ` Stephen Boyd 2016-02-26 19:33 ` Stephen Boyd 2016-03-01 19:32 ` Lina Iyer 2016-03-01 19:32 ` Lina Iyer 2016-03-01 19:35 ` Stephen Boyd 2016-03-01 19:35 ` Stephen Boyd 2016-02-12 20:50 ` [RFC v2 08/12] Documentation / cpu_domains: Describe CPU PM domains setup and governor Lina Iyer 2016-02-12 20:50 ` Lina Iyer 2016-02-26 19:43 ` Stephen Boyd 2016-02-26 19:43 ` Stephen Boyd 2016-03-01 19:36 ` Lina Iyer 2016-03-01 19:36 ` Lina Iyer 2016-02-12 20:50 ` [RFC v2 09/12] drivers: firmware: psci: Allow OS Initiated suspend mode Lina Iyer 2016-02-12 20:50 ` Lina Iyer 2016-02-12 20:50 ` [RFC v2 10/12] ARM64: psci: Support cluster idle states for OS-Initiated Lina Iyer 2016-02-12 20:50 ` Lina Iyer 2016-02-12 20:50 ` [RFC v2 11/12] ARM64: dts: Add PSCI cpuidle support for MSM8916 Lina Iyer 2016-02-12 20:50 ` Lina Iyer 2016-02-12 20:50 ` [RFC v2 12/12] ARM64: dts: Define CPU power domain " Lina Iyer 2016-02-12 20:50 ` Lina Iyer 2016-02-26 19:50 ` Stephen Boyd 2016-02-26 19:50 ` Stephen Boyd 2016-03-01 19:41 ` Lina Iyer 2016-03-01 19:41 ` Lina Iyer
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=1455310238-8963-6-git-send-email-lina.iyer@linaro.org \ --to=lina.iyer@linaro.org \ --cc=agross@codeaurora.org \ --cc=ahaslam@baylibre.com \ --cc=geert@linux-m68k.org \ --cc=k.kozlowski@samsung.com \ --cc=khilman@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-pm@vger.kernel.org \ --cc=lorenzo.pieralisi@arm.com \ --cc=msivasub@codeaurora.org \ --cc=mtitinger@baylibre.com \ --cc=rjw@rjwysocki.net \ --cc=sboyd@codeaurora.org \ --cc=tglx@linutronix.de \ --cc=ulf.hansson@linaro.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: linkBe 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.