[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1402071856420.21991@ionos.tec.linutronix.de>
Date: Fri, 7 Feb 2014 18:57:51 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Preeti U Murthy <preeti@...ux.vnet.ibm.com>
cc: fengguang.wu@...el.com, mingo@...nel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] time/cpuidle:Fixup fallout from hrtimer broadcast mode
inclusion
On Fri, 7 Feb 2014, Preeti U Murthy wrote:
> The broadcast timer registration has to be done only when
> GENERIC_CLOCKEVENTS_BROADCAST and TICK_ONESHOT config options are enabled.
Then we should compile that file only when those options are
enabled. Where is the point to compile that code w/o the registration
function?
> Also fix max_delta_ticks value for the pseudo clock device.
>
> Reported-by: Fengguang Wu <fengguang.wu@...el.com>
> Signed-off-by: Preeti U Murthy <preeti@...ux.vnet.ibm.com>
> Cc: Thomas Gleixner <tglx@...utronix.de>
> Cc: Ingo Molnar <mingo@...nel.org>
> ---
>
> kernel/time/tick-broadcast-hrtimer.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/time/tick-broadcast-hrtimer.c b/kernel/time/tick-broadcast-hrtimer.c
> index 5591aaa..bc383ac 100644
> --- a/kernel/time/tick-broadcast-hrtimer.c
> +++ b/kernel/time/tick-broadcast-hrtimer.c
> @@ -81,7 +81,7 @@ static struct clock_event_device ce_broadcast_hrtimer = {
> .min_delta_ns = 1,
> .max_delta_ns = KTIME_MAX,
> .min_delta_ticks = 1,
> - .max_delta_ticks = KTIME_MAX,
> + .max_delta_ticks = ULONG_MAX,
> .mult = 1,
> .shift = 0,
> .cpumask = cpu_all_mask,
> @@ -102,9 +102,11 @@ static enum hrtimer_restart bc_handler(struct hrtimer *t)
> return HRTIMER_RESTART;
> }
>
> +#if defined(CONFIG_GENERIC_CLOCKEVENTS_BROADCAST) && defined(CONFIG_TICK_ONESHOT)
> void tick_setup_hrtimer_broadcast(void)
> {
> hrtimer_init(&bctimer, CLOCK_MONOTONIC, HRTIMER_MODE_ABS);
> bctimer.function = bc_handler;
> clockevents_register_device(&ce_broadcast_hrtimer);
> }
> +#endif
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists