All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikael Beckius <mikael.beckius@windriver.com>
To: anna-maria@linutronix.de
Cc: linux-kernel@vger.kernel.org, mikael.beckius@windriver.com,
	tglx@linutronix.de
Subject: Sv: [PATCH] hrtimer: Update softirq_expires_next correctly after __hrtimer_get_next_event()
Date: Thu, 25 Feb 2021 12:18:51 +0100	[thread overview]
Message-ID: <20210225111851.8432-1-mikael.beckius@windriver.com> (raw)
In-Reply-To: <20210223160240.27518-1-anna-maria@linutronix.de>

> Micke, please test this patch - it is compile tested only...

Thanks Anna-Maria, it seems to work equally good or better than the change
I suggested in preventing interrupt storms. After running a test I created,
based on traces from a live system, several thousands of iterations
there are no reproductions. Normally both issues will reproduce within
seconds after only a few iterations.

Also by looking at the source code it seems like your patch should do the
trick.

Micke

  reply	other threads:[~2021-02-25 11:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28 14:02 [PATCH] hrtimer: Interrupt storm on clock_settime Mikael Beckius
2021-02-05 15:45 ` Thomas Gleixner
2021-02-12 13:38   ` Sv: " Beckius, Mikael
2021-02-23 15:53     ` Anna-Maria Behnsen
2021-02-25 11:18       ` Sv: " Mikael Beckius
2021-03-01  9:13         ` Thomas Gleixner
2021-02-23 16:02     ` [PATCH] hrtimer: Update softirq_expires_next correctly after __hrtimer_get_next_event() Anna-Maria Behnsen
2021-02-25 11:18       ` Mikael Beckius [this message]
2021-03-01  9:23       ` [tip: timers/urgent] " tip-bot2 for Anna-Maria Behnsen
2021-03-06 12:00       ` tip-bot2 for Anna-Maria Behnsen
2021-03-08  8:41       ` tip-bot2 for Anna-Maria Behnsen
2021-02-09 15:22 ` [tip: timers/urgent] hrtimer: Update softirq_expires_next correctly in hrtimer_force_reprogram() tip-bot2 for Mikael Beckius

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210225111851.8432-1-mikael.beckius@windriver.com \
    --to=mikael.beckius@windriver.com \
    --cc=anna-maria@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.