Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1740785
| From | Anna-Maria Gleixner <anna-maria@linutronix.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 17/25] hrtimer: Implementation of softirq hrtimer handling |
| Date | 2017-09-27 16:30 +0200 |
| Message-ID | <uulvA-4kL-21@gated-at.bofh.it> (permalink) |
| References | <ukwLD-5Ay-3@gated-at.bofh.it> <ukwLD-5Ay-1@gated-at.bofh.it> <utZEL-6pY-53@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue, 26 Sep 2017, Peter Zijlstra wrote:
> On Thu, Aug 31, 2017 at 12:23:42PM -0000, Anna-Maria Gleixner wrote:
> > static void __run_hrtimer(struct hrtimer_cpu_base *cpu_base,
> > struct hrtimer_clock_base *base,
> > - struct hrtimer *timer, ktime_t *now)
> > + struct hrtimer *timer, ktime_t *now,
> > + bool hardirq)
> > {
> > enum hrtimer_restart (*fn)(struct hrtimer *);
> > int restart;
> > @@ -1241,11 +1298,19 @@ static void __run_hrtimer(struct hrtimer
> > * protected against migration to a different CPU even if the lock
> > * is dropped.
> > */
> > - raw_spin_unlock(&cpu_base->lock);
> > + if (hardirq)
> > + raw_spin_unlock(&cpu_base->lock);
> > + else
> > + raw_spin_unlock_irq(&cpu_base->lock);
> > +
> > trace_hrtimer_expire_entry(timer, now);
> > restart = fn(timer);
> > trace_hrtimer_expire_exit(timer);
> > - raw_spin_lock(&cpu_base->lock);
> > +
> > + if (hardirq)
> > + raw_spin_lock(&cpu_base->lock);
> > + else
> > + raw_spin_lock_irq(&cpu_base->lock);
> >
>
> That's just nasty...
>
I know and Thomas was unhappy about that as well, but we did not come
up with a better solution.
The nasty alternative is:
static void __run_hrtimer(struct hrtimer_cpu_base *cpu_base,
struct hrtimer_clock_base *base,
- struct hrtimer *timer, ktime_t *now)
+ struct hrtimer *timer, ktime_t *now,
+ unsigned long flags)
...
- raw_spin_unlock(&cpu_base->lock);
+ raw_spin_unlock_irqrestore(&cpu_base->lock, flags);
...
- raw_spin_lock(&cpu_base->lock);
+ raw_spin_lock_irq(&cpu_base->lock, flags);
and hand in flags from the callsites via local_save_flags().
We wanted to avoid the pointless lock_irq for the interrupt context,
but yes the conditional is equally bad.
Anna-Maria
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Re: [PATCH 17/25] hrtimer: Implementation of softirq hrtimer handling Anna-Maria Gleixner <anna-maria@linutronix.de> - 2017-09-27 16:30 +0200 Re: [PATCH 17/25] hrtimer: Implementation of softirq hrtimer handling Peter Zijlstra <peterz@infradead.org> - 2017-09-27 18:50 +0200
csiph-web