linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>,
	Florian Fainelli <f.fainelli@gmail.com>
Cc: Joel Fernandes <joel@joelfernandes.org>,
	Boqun Feng <boqun.feng@gmail.com>,
	Anna-Maria Behnsen <anna-maria@linutronix.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, kernel-team@meta.com,
	paulmck@kernel.org, mingo@kernel.org, rcu@vger.kernel.org,
	neeraj.upadhyay@amd.com, urezki@gmail.com,
	qiang.zhang1211@gmail.com, frederic@kernel.org,
	bigeasy@linutronix.de, chenzhongjin@huawei.com,
	yangjihong1@huawei.com, rostedt@goodmis.org,
	Justin Chen <justin.chen@broadcom.com>
Subject: Re: Unexplained long boot delays [Was Re: [GIT PULL] RCU changes for v6.9]
Date: Thu, 14 Mar 2024 10:03:55 +0100	[thread overview]
Message-ID: <87o7bhmbgk.ffs@tglx> (raw)
In-Reply-To: <ZfIh33YAYkLaDeAS@shell.armlinux.org.uk>

On Wed, Mar 13 2024 at 21:59, Russell King (Oracle) wrote:
> On Wed, Mar 13, 2024 at 02:30:43PM -0700, Florian Fainelli wrote:
> I haven't understood the code there yet, and how it would interact with
> arch code, but one thing that immediately jumps out to me is this:
>
> "    As long as a CPU is busy it expires both local and global timers. When a
>     CPU goes idle it arms for the first expiring local timer."
>
> So are local timers "armed" when they are enqueued while the cpu is
> "busy" during initialisation, and will they expire, and will that
> expiry be delivered in a timely manner?

The local timers are timers which are pinned on a CPU. Global ones do
not care about the CPU they expire on.

So if the CPU goes idle then it arms for the first local timer. If the
first global timer expires after the first local, nothing to see. If it
expires before then that timer is queued in the migration hierarchy and
some other busy CPU will take care of it. If the last CPU goes idle then
it has to arm for the first timer (it's own local, global and the
hierarchy). So it's all covered in theory, but there seems to be an
issue somewhere. We'll figure it out.

Thanks,

        tglx



      parent reply	other threads:[~2024-03-14  9:03 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08 17:15 [GIT PULL] RCU changes for v6.9 Boqun Feng
2024-03-11 19:43 ` pr-tracker-bot
2024-03-12 20:32 ` Unexplained long boot delays [Was Re: [GIT PULL] RCU changes for v6.9] Florian Fainelli
2024-03-12 21:01   ` Frederic Weisbecker
2024-03-12 21:15     ` Paul E. McKenney
2024-03-12 21:35       ` Florian Fainelli
2024-03-12 22:05     ` Florian Fainelli
2024-03-12 21:07   ` Boqun Feng
2024-03-12 21:34     ` Florian Fainelli
2024-03-12 21:44       ` Linus Torvalds
2024-03-12 23:48         ` Boqun Feng
2024-03-13 16:01           ` Joel Fernandes
2024-03-13 21:30             ` Florian Fainelli
2024-03-13 21:59               ` Russell King (Oracle)
2024-03-13 22:04                 ` Florian Fainelli
2024-03-13 22:49                   ` Russell King (Oracle)
2024-03-13 23:29                     ` Florian Fainelli
2024-03-14  1:15                       ` Linus Torvalds
2024-03-14  1:22                         ` Florian Fainelli
2024-03-13 22:52                   ` Frederic Weisbecker
2024-03-14  3:44                     ` Florian Fainelli
2024-03-14  5:12                       ` Boqun Feng
2024-03-14  6:33                         ` Boqun Feng
2024-03-14  9:32                           ` Thomas Gleixner
2024-03-14  9:11                       ` Thomas Gleixner
2024-03-14 10:41                       ` Frederic Weisbecker
2024-03-14 18:35                         ` Florian Fainelli
2024-03-14 18:51                           ` Boqun Feng
2024-03-14 19:09                             ` Florian Fainelli
2024-03-14 20:45                               ` Thomas Gleixner
2024-03-14 21:21                                 ` Thomas Gleixner
2024-03-14 21:53                                   ` Florian Fainelli
2024-03-14 22:51                                     ` Thomas Gleixner
2024-03-14 21:58                                   ` Thomas Gleixner
2024-03-14 22:05                                   ` Boqun Feng
2024-03-14 22:10                                     ` Boqun Feng
2024-03-15  1:14                                     ` [PATCH] timer/migration: Remove buggy early return on deactivation [was Re: Unexplained long boot delays [Was Re: [GIT PULL] RCU changes for v6.9]] Frederic Weisbecker
2024-03-15  1:20                                       ` Frederic Weisbecker
2024-03-15 13:44                                       ` Florian Fainelli
2024-03-16 19:06                                       ` [tip: timers/urgent] timer/migration: Remove buggy early return on deactivation tip-bot2 for Frederic Weisbecker
2024-03-26 16:41                                       ` [PATCH] timer/migration: Remove buggy early return on deactivation [was Re: Unexplained long boot delays [Was Re: [GIT PULL] RCU changes for v6.9]] Anna-Maria Behnsen
2024-03-26 17:18                                         ` Frederic Weisbecker
2024-04-04 16:50                                           ` [PATCH] timers/migration: Return early on deactivation Anna-Maria Behnsen
2024-04-04 22:19                                             ` Frederic Weisbecker
2024-04-05  8:53                                               ` [PATCH v2] " Anna-Maria Behnsen
2024-04-05  9:11                                                 ` [tip: timers/urgent] " tip-bot2 for Anna-Maria Behnsen
2024-03-14  9:03                 ` Thomas Gleixner [this message]

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=87o7bhmbgk.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=anna-maria@linutronix.de \
    --cc=bigeasy@linutronix.de \
    --cc=boqun.feng@gmail.com \
    --cc=chenzhongjin@huawei.com \
    --cc=f.fainelli@gmail.com \
    --cc=frederic@kernel.org \
    --cc=joel@joelfernandes.org \
    --cc=justin.chen@broadcom.com \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mingo@kernel.org \
    --cc=neeraj.upadhyay@amd.com \
    --cc=paulmck@kernel.org \
    --cc=qiang.zhang1211@gmail.com \
    --cc=rcu@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.org \
    --cc=urezki@gmail.com \
    --cc=yangjihong1@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).