linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] arm: kernel: initialize broadcast hrtimer based clock event device
@ 2019-11-12 12:06 Benjamin Gaignard
  2019-11-12 14:48 ` Thomas Gleixner
  0 siblings, 1 reply; 5+ messages in thread
From: Benjamin Gaignard @ 2019-11-12 12:06 UTC (permalink / raw)
  To: linux, tglx, gregkh, rmk+kernel
  Cc: linux-arm-kernel, linux-kernel, linux-stm32, Benjamin Gaignard

On platforms implementing CPU power management, the CPUidle subsystem
can allow CPUs to enter idle states where local timers logic is lost on power
down. To keep the software timers functional the kernel relies on an
always-on broadcast timer to be present in the platform to relay the
interrupt signalling the timer expiries.

For platforms implementing CPU core gating that do not implement an always-on
HW timer or implement it in a broken way, this patch adds code to initialize
the kernel hrtimer based clock event device upon boot (which can be chosen as
tick broadcast device by the kernel).
It relies on a dynamically chosen CPU to be always powered-up. This CPU then
relays the timer interrupt to CPUs in deep-idle states through its HW local
timer device.

Having a CPU always-on has implications on power management platform
capabilities and makes CPUidle suboptimal, since at least a CPU is kept
always in a shallow idle state by the kernel to relay timer interrupts,
but at least leaves the kernel with a functional system with some working
power management capabilities.

The hrtimer based clock event device is unconditionally registered, but
has the lowest possible rating such that any broadcast-capable HW clock
event device present will be chosen in preference as the tick broadcast
device.

Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
---
Note:
- The same reasons lead to same patch than for arm64 so I have copy the
  commit message from: 9358d755bd5c ("arm64: kernel: initialize broadcast
  hrtimer based clock event device")
 arch/arm/kernel/time.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/arch/arm/kernel/time.c b/arch/arm/kernel/time.c
index b996b2cf0703..dddc7ebf4db4 100644
--- a/arch/arm/kernel/time.c
+++ b/arch/arm/kernel/time.c
@@ -9,6 +9,7 @@
  *  reading the RTC at bootup, etc...
  */
 #include <linux/clk-provider.h>
+#include <linux/clockchips.h>
 #include <linux/clocksource.h>
 #include <linux/errno.h>
 #include <linux/export.h>
@@ -107,5 +108,6 @@ void __init time_init(void)
 		of_clk_init(NULL);
 #endif
 		timer_probe();
+		tick_setup_hrtimer_broadcast();
 	}
 }
-- 
2.15.0


^ permalink raw reply related	[flat|nested] 5+ messages in thread

* Re: [PATCH] arm: kernel: initialize broadcast hrtimer based clock event device
  2019-11-12 12:06 [PATCH] arm: kernel: initialize broadcast hrtimer based clock event device Benjamin Gaignard
@ 2019-11-12 14:48 ` Thomas Gleixner
  2019-11-12 14:55   ` Russell King - ARM Linux admin
  0 siblings, 1 reply; 5+ messages in thread
From: Thomas Gleixner @ 2019-11-12 14:48 UTC (permalink / raw)
  To: Benjamin Gaignard
  Cc: linux, gregkh, rmk+kernel, linux-arm-kernel, linux-kernel, linux-stm32

On Tue, 12 Nov 2019, Benjamin Gaignard wrote:

> On platforms implementing CPU power management, the CPUidle subsystem
> can allow CPUs to enter idle states where local timers logic is lost on power
> down. To keep the software timers functional the kernel relies on an
> always-on broadcast timer to be present in the platform to relay the
> interrupt signalling the timer expiries.
> 
> For platforms implementing CPU core gating that do not implement an always-on
> HW timer or implement it in a broken way, this patch adds code to initialize
> the kernel hrtimer based clock event device upon boot (which can be chosen as
> tick broadcast device by the kernel).
> It relies on a dynamically chosen CPU to be always powered-up. This CPU then
> relays the timer interrupt to CPUs in deep-idle states through its HW local
> timer device.
> 
> Having a CPU always-on has implications on power management platform
> capabilities and makes CPUidle suboptimal, since at least a CPU is kept
> always in a shallow idle state by the kernel to relay timer interrupts,
> but at least leaves the kernel with a functional system with some working
> power management capabilities.
> 
> The hrtimer based clock event device is unconditionally registered, but
> has the lowest possible rating such that any broadcast-capable HW clock
> event device present will be chosen in preference as the tick broadcast
> device.
> 
> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>

Reviewed-by: Thomas Gleixner <tglx@linutronix.de>

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH] arm: kernel: initialize broadcast hrtimer based clock event device
  2019-11-12 14:48 ` Thomas Gleixner
@ 2019-11-12 14:55   ` Russell King - ARM Linux admin
  0 siblings, 0 replies; 5+ messages in thread
From: Russell King - ARM Linux admin @ 2019-11-12 14:55 UTC (permalink / raw)
  To: Thomas Gleixner
  Cc: Benjamin Gaignard, gregkh, linux-arm-kernel, linux-kernel, linux-stm32

On Tue, Nov 12, 2019 at 03:48:10PM +0100, Thomas Gleixner wrote:
> On Tue, 12 Nov 2019, Benjamin Gaignard wrote:
> 
> > On platforms implementing CPU power management, the CPUidle subsystem
> > can allow CPUs to enter idle states where local timers logic is lost on power
> > down. To keep the software timers functional the kernel relies on an
> > always-on broadcast timer to be present in the platform to relay the
> > interrupt signalling the timer expiries.
> > 
> > For platforms implementing CPU core gating that do not implement an always-on
> > HW timer or implement it in a broken way, this patch adds code to initialize
> > the kernel hrtimer based clock event device upon boot (which can be chosen as
> > tick broadcast device by the kernel).
> > It relies on a dynamically chosen CPU to be always powered-up. This CPU then
> > relays the timer interrupt to CPUs in deep-idle states through its HW local
> > timer device.
> > 
> > Having a CPU always-on has implications on power management platform
> > capabilities and makes CPUidle suboptimal, since at least a CPU is kept
> > always in a shallow idle state by the kernel to relay timer interrupts,
> > but at least leaves the kernel with a functional system with some working
> > power management capabilities.
> > 
> > The hrtimer based clock event device is unconditionally registered, but
> > has the lowest possible rating such that any broadcast-capable HW clock
> > event device present will be chosen in preference as the tick broadcast
> > device.
> > 
> > Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
> 
> Reviewed-by: Thomas Gleixner <tglx@linutronix.de>

Thanks.  Benjamin, please put it in the patch system, thanks.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [PATCH] arm: kernel: initialize broadcast hrtimer based clock event device
  2019-10-15  8:41 Benjamin Gaignard
@ 2019-10-29 12:43 ` Benjamin Gaignard
  0 siblings, 0 replies; 5+ messages in thread
From: Benjamin Gaignard @ 2019-10-29 12:43 UTC (permalink / raw)
  To: Benjamin Gaignard
  Cc: Russell King - ARM Linux, Thomas Gleixner, Greg Kroah-Hartman,
	Linux Kernel Mailing List, Linux ARM, linux-stm32, maz

Le mar. 15 oct. 2019 à 10:42, Benjamin Gaignard
<benjamin.gaignard@st.com> a écrit :
>
> On platforms implementing CPU power management, the CPUidle subsystem
> can allow CPUs to enter idle states where local timers logic is lost on power
> down. To keep the software timers functional the kernel relies on an
> always-on broadcast timer to be present in the platform to relay the
> interrupt signalling the timer expiries.
>
> For platforms implementing CPU core gating that do not implement an always-on
> HW timer or implement it in a broken way, this patch adds code to initialize
> the kernel hrtimer based clock event device upon boot (which can be chosen as
> tick broadcast device by the kernel).
> It relies on a dynamically chosen CPU to be always powered-up. This CPU then
> relays the timer interrupt to CPUs in deep-idle states through its HW local
> timer device.
>
> Having a CPU always-on has implications on power management platform
> capabilities and makes CPUidle suboptimal, since at least a CPU is kept
> always in a shallow idle state by the kernel to relay timer interrupts,
> but at least leaves the kernel with a functional system with some working
> power management capabilities.
>
> The hrtimer based clock event device is unconditionally registered, but
> has the lowest possible rating such that any broadcast-capable HW clock
> event device present will be chosen in preference as the tick broadcast
> device.

Gentle ping,

Thanks,
Benjamin
>
> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
> ---
> Note:
> - The same reasons lead to same patch than for arm64 so I have copy the
>   commit message from: 9358d755bd5c ("arm64: kernel: initialize broadcast
>   hrtimer based clock event device")
>  arch/arm/kernel/time.c | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm/kernel/time.c b/arch/arm/kernel/time.c
> index b996b2cf0703..dddc7ebf4db4 100644
> --- a/arch/arm/kernel/time.c
> +++ b/arch/arm/kernel/time.c
> @@ -9,6 +9,7 @@
>   *  reading the RTC at bootup, etc...
>   */
>  #include <linux/clk-provider.h>
> +#include <linux/clockchips.h>
>  #include <linux/clocksource.h>
>  #include <linux/errno.h>
>  #include <linux/export.h>
> @@ -107,5 +108,6 @@ void __init time_init(void)
>                 of_clk_init(NULL);
>  #endif
>                 timer_probe();
> +               tick_setup_hrtimer_broadcast();
>         }
>  }
> --
> 2.15.0
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [PATCH] arm: kernel: initialize broadcast hrtimer based clock event device
@ 2019-10-15  8:41 Benjamin Gaignard
  2019-10-29 12:43 ` Benjamin Gaignard
  0 siblings, 1 reply; 5+ messages in thread
From: Benjamin Gaignard @ 2019-10-15  8:41 UTC (permalink / raw)
  To: linux, tglx, gregkh
  Cc: linux-arm-kernel, linux-kernel, linux-stm32, Benjamin Gaignard

On platforms implementing CPU power management, the CPUidle subsystem
can allow CPUs to enter idle states where local timers logic is lost on power
down. To keep the software timers functional the kernel relies on an
always-on broadcast timer to be present in the platform to relay the
interrupt signalling the timer expiries.

For platforms implementing CPU core gating that do not implement an always-on
HW timer or implement it in a broken way, this patch adds code to initialize
the kernel hrtimer based clock event device upon boot (which can be chosen as
tick broadcast device by the kernel).
It relies on a dynamically chosen CPU to be always powered-up. This CPU then
relays the timer interrupt to CPUs in deep-idle states through its HW local
timer device.

Having a CPU always-on has implications on power management platform
capabilities and makes CPUidle suboptimal, since at least a CPU is kept
always in a shallow idle state by the kernel to relay timer interrupts,
but at least leaves the kernel with a functional system with some working
power management capabilities.

The hrtimer based clock event device is unconditionally registered, but
has the lowest possible rating such that any broadcast-capable HW clock
event device present will be chosen in preference as the tick broadcast
device.

Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
---
Note:
- The same reasons lead to same patch than for arm64 so I have copy the
  commit message from: 9358d755bd5c ("arm64: kernel: initialize broadcast
  hrtimer based clock event device")
 arch/arm/kernel/time.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/arch/arm/kernel/time.c b/arch/arm/kernel/time.c
index b996b2cf0703..dddc7ebf4db4 100644
--- a/arch/arm/kernel/time.c
+++ b/arch/arm/kernel/time.c
@@ -9,6 +9,7 @@
  *  reading the RTC at bootup, etc...
  */
 #include <linux/clk-provider.h>
+#include <linux/clockchips.h>
 #include <linux/clocksource.h>
 #include <linux/errno.h>
 #include <linux/export.h>
@@ -107,5 +108,6 @@ void __init time_init(void)
 		of_clk_init(NULL);
 #endif
 		timer_probe();
+		tick_setup_hrtimer_broadcast();
 	}
 }
-- 
2.15.0


^ permalink raw reply related	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2019-11-12 14:56 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-12 12:06 [PATCH] arm: kernel: initialize broadcast hrtimer based clock event device Benjamin Gaignard
2019-11-12 14:48 ` Thomas Gleixner
2019-11-12 14:55   ` Russell King - ARM Linux admin
  -- strict thread matches above, loose matches on Subject: below --
2019-10-15  8:41 Benjamin Gaignard
2019-10-29 12:43 ` Benjamin Gaignard

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