[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1983406.XYedcDVy8E@ada>
Date: Tue, 27 Aug 2019 16:26:20 +0200
From: Alexander Dahl <ada@...rsis.com>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: Julien Grall <julien.grall@....com>,
linux-rt-users@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [ANNOUNCE] v5.2.10-rt5
Hello Sebastian,
Am Dienstag, 27. August 2019, 15:22:01 CEST schrieb Sebastian Andrzej Siewior:
> of course, !SMP. What about this:
>
> diff --git a/kernel/time/hrtimer.c b/kernel/time/hrtimer.c
> --- a/kernel/time/hrtimer.c
> +++ b/kernel/time/hrtimer.c
> @@ -934,7 +934,11 @@ void hrtimer_grab_expiry_lock(const struct hrtimer
> *timer) {
> struct hrtimer_clock_base *base = READ_ONCE(timer->base);
>
> +#ifdef CONFIG_SMP
> if (timer->is_soft && base != &migration_base) {
> +#else
> + if (timer->is_soft && base && base->cpu_base) {
> +#endif
> spin_lock(&base->cpu_base->softirq_expiry_lock);
> spin_unlock(&base->cpu_base->softirq_expiry_lock);
> }
Build error is gone and target system boots successfully, seems to work fine
at first sight. Thanks for the quick response.
Greets
Alex
Powered by blists - more mailing lists