Re: [PATCH] arm: Initialize hrtimer-based broadcast clockevent
On 2018-04-04 17:54, Jan Kiszka wrote: > On 2018-03-01 07:04, Jan Kiszka wrote: >> On 2018-01-22 07:06, Jan Kiszka wrote: >>> Analogously to 9358d755bd5c, this registers a broadcast clockevent in >>> case no hardware broadcast timer is available and the per-CPU timers can >>> be stopped in deep power states. >>> >>> Partitions of the Jailhouse hypervisor fall in this category. >>> Registering the workaround timer allows to enter high-resolution mode in >>> that case. >>> >>> Signed-off-by: Jan Kiszka >>> --- >>> arch/arm/kernel/time.c | 3 +++ >>> 1 file changed, 3 insertions(+) >>> >>> diff --git a/arch/arm/kernel/time.c b/arch/arm/kernel/time.c >>> index 629f8e9981f1..0a45d861ef8e 100644 >>> --- a/arch/arm/kernel/time.c >>> +++ b/arch/arm/kernel/time.c >>> @@ -12,6 +12,7 @@ >>> * reading the RTC at bootup, etc... >>> */ >>> #include >>> +#include >>> #include >>> #include >>> #include >>> @@ -121,5 +122,7 @@ void __init time_init(void) >>> of_clk_init(NULL); >>> #endif >>> timer_probe(); >>> + >>> + tick_setup_hrtimer_broadcast(); >>> } >>> } >>> >> >> Gentle ping, just to avoid that this falls through the cracks because >> it's so small. >> > > 2nd ping. Should this patch be routed via ARM or rather some tip/timers > tree? > 3rd try: Could someone have a look at this and merge it - or at least ack it in order to move forward? Thanks, Jan
Re: [PATCH] arm: Initialize hrtimer-based broadcast clockevent
On 2018-03-01 07:04, Jan Kiszka wrote: > On 2018-01-22 07:06, Jan Kiszka wrote: >> Analogously to 9358d755bd5c, this registers a broadcast clockevent in >> case no hardware broadcast timer is available and the per-CPU timers can >> be stopped in deep power states. >> >> Partitions of the Jailhouse hypervisor fall in this category. >> Registering the workaround timer allows to enter high-resolution mode in >> that case. >> >> Signed-off-by: Jan Kiszka >> --- >> arch/arm/kernel/time.c | 3 +++ >> 1 file changed, 3 insertions(+) >> >> diff --git a/arch/arm/kernel/time.c b/arch/arm/kernel/time.c >> index 629f8e9981f1..0a45d861ef8e 100644 >> --- a/arch/arm/kernel/time.c >> +++ b/arch/arm/kernel/time.c >> @@ -12,6 +12,7 @@ >> * reading the RTC at bootup, etc... >> */ >> #include >> +#include >> #include >> #include >> #include >> @@ -121,5 +122,7 @@ void __init time_init(void) >> of_clk_init(NULL); >> #endif >> timer_probe(); >> + >> +tick_setup_hrtimer_broadcast(); >> } >> } >> > > Gentle ping, just to avoid that this falls through the cracks because > it's so small. > 2nd ping. Should this patch be routed via ARM or rather some tip/timers tree? Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux
Re: [PATCH] arm: Initialize hrtimer-based broadcast clockevent
On 2018-01-22 07:06, Jan Kiszka wrote: > Analogously to 9358d755bd5c, this registers a broadcast clockevent in > case no hardware broadcast timer is available and the per-CPU timers can > be stopped in deep power states. > > Partitions of the Jailhouse hypervisor fall in this category. > Registering the workaround timer allows to enter high-resolution mode in > that case. > > Signed-off-by: Jan Kiszka > --- > arch/arm/kernel/time.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/arch/arm/kernel/time.c b/arch/arm/kernel/time.c > index 629f8e9981f1..0a45d861ef8e 100644 > --- a/arch/arm/kernel/time.c > +++ b/arch/arm/kernel/time.c > @@ -12,6 +12,7 @@ > * reading the RTC at bootup, etc... > */ > #include > +#include > #include > #include > #include > @@ -121,5 +122,7 @@ void __init time_init(void) > of_clk_init(NULL); > #endif > timer_probe(); > + > + tick_setup_hrtimer_broadcast(); > } > } > Gentle ping, just to avoid that this falls through the cracks because it's so small. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux