From: Lorenzo Colitti <lorenzo@google.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Greg KH" <gregkh@linuxfoundation.org>,
"Maciej Żenczykowski" <zenczykowski@gmail.com>,
"Ingo Molnar" <mingo@kernel.org>,
"Anna-Maria Behnsen" <anna-maria@linutronix.de>,
lkml <linux-kernel@vger.kernel.org>,
mikael.beckius@windriver.com,
"Maciej Żenczykowski" <maze@google.com>
Subject: Re: [PATCH] hrtimer: Update softirq_expires_next correctly after __hrtimer_get_next_event()
Date: Tue, 20 Apr 2021 17:15:03 +0900 [thread overview]
Message-ID: <CAKD1Yr1o=zN5K9PaB3wag5xOS2oY6AzEsV6dmL7pnTysK_GOhA@mail.gmail.com> (raw)
In-Reply-To: <87r1jbv6jc.ffs@nanos.tec.linutronix.de>
On Fri, Apr 16, 2021 at 1:47 AM Thomas Gleixner <tglx@linutronix.de> wrote:
> Enable tracing and enable the following tracepoints:
> [...]
Sorry for the delay. I had to learn a bit about how to use the tracing
infrastructure. I don't know if I can post here, but to my untrained
eye, one big difference between the old (fast) code and the new (slow)
code is that the new code calls tick_program_event() much more. It
looks like that makes most of the difference.
With the old code, hrtimer_start_range_ns almost never calls
tick_program_event at all, but the new code seems to call it twice on
every timer update.
next prev parent reply other threads:[~2021-04-20 8:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 16:55 [PATCH] hrtimer: Update softirq_expires_next correctly after __hrtimer_get_next_event() Maciej Żenczykowski
2021-04-13 17:14 ` Greg KH
2021-04-14 2:49 ` Lorenzo Colitti
2021-04-15 16:47 ` Thomas Gleixner
2021-04-20 3:12 ` Maciej Żenczykowski
2021-04-20 6:44 ` Thomas Gleixner
2021-04-20 8:15 ` Lorenzo Colitti [this message]
2021-04-20 14:19 ` Thomas Gleixner
2021-04-21 14:08 ` Lorenzo Colitti
2021-04-21 14:40 ` Lorenzo Colitti
2021-04-21 15:22 ` Greg KH
2021-04-22 0:08 ` Thomas Gleixner
2021-04-22 10:07 ` Thomas Gleixner
2021-04-22 14:20 ` Lorenzo Colitti
2021-04-22 15:35 ` Thomas Gleixner
2021-04-26 8:49 ` [PATCH] hrtimer: Avoid double reprogramming in __hrtimer_start_range_ns() Thomas Gleixner
2021-04-26 9:40 ` Peter Zijlstra
2021-04-26 12:25 ` Peter Zijlstra
2021-05-14 19:29 ` Thomas Gleixner
2021-04-26 12:33 ` Thomas Gleixner
2021-04-26 12:40 ` Peter Zijlstra
2021-04-26 14:27 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2021-02-12 13:38 Sv: [PATCH] hrtimer: Interrupt storm on clock_settime Beckius, Mikael
2021-02-23 16:02 ` [PATCH] hrtimer: Update softirq_expires_next correctly after __hrtimer_get_next_event() Anna-Maria Behnsen
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='CAKD1Yr1o=zN5K9PaB3wag5xOS2oY6AzEsV6dmL7pnTysK_GOhA@mail.gmail.com' \
--to=lorenzo@google.com \
--cc=anna-maria@linutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maze@google.com \
--cc=mikael.beckius@windriver.com \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=zenczykowski@gmail.com \
/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.