public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <frederic@kernel.org>
To: Anna-Maria Behnsen <anna-maria@linutronix.de>
Cc: Boqun Feng <boqun.feng@gmail.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"Russell King (Oracle)" <linux@armlinux.org.uk>,
	Joel Fernandes <joel@joelfernandes.org>,
	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, bigeasy@linutronix.de,
	chenzhongjin@huawei.com, yangjihong1@huawei.com,
	rostedt@goodmis.org, Justin Chen <justin.chen@broadcom.com>
Subject: Re: [PATCH] timer/migration: Remove buggy early return on deactivation [was Re: Unexplained long boot delays [Was Re: [GIT PULL] RCU changes for v6.9]]
Date: Tue, 26 Mar 2024 18:18:40 +0100	[thread overview]
Message-ID: <ZgMDcGOagCjfIB3i@localhost.localdomain> (raw)
In-Reply-To: <87zfulrlnn.fsf@somnus>

Le Tue, Mar 26, 2024 at 05:41:00PM +0100, Anna-Maria Behnsen a écrit :
> Frederic Weisbecker <frederic@kernel.org> writes:
> Now propagation goes on as GRP0:0 is completely idle. When executing
> tmigr_update_events() in the next step of walking the hierarchy via
> tmigr_inactive_up(), the arguments for tmigr_update_events() are set in
> the following way:
> 
>   group = GRP1:0
>   child = GRP0:0
> 
> Then at the begin of tmigr_update_events() the group event of child is
> updated - so all ignored events are removed (T0i), and the
> child->groupevt and child->next_expiry is updated with T1. This
> reevaluated child->groupevt is then queued/updated in the GRP1:0
> timerqueue.
> 
> So T1 will be handled!
> 
> As there is no parent, the top level group event is updated (see goto
> label "check_toplvl") and T1 will be still the first event.

Bah! Good point, I got confused there...

> 
> > Fix those issues with removing the buggy related early return. Ignored
> > child events must not prevent from evaluating the other events within
> > the same group.
> 
> I would prefere to keep this early return but skip it, when there is
> !group->parent (only a single level in hierarchy).
> 
> Then it would prevent taking the group lock and making some random
> event updates which are done nevertheless on the next iteration of the
> hierarchy walk.

Ok sounds like a good plan!

Thanks.

> 
> Thanks,
> 
> 	Anna-Maria
> 

  reply	other threads:[~2024-03-26 17:18 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 [this message]
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                 ` Unexplained long boot delays [Was Re: [GIT PULL] RCU changes for v6.9] Thomas Gleixner

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=ZgMDcGOagCjfIB3i@localhost.localdomain \
    --to=frederic@kernel.org \
    --cc=anna-maria@linutronix.de \
    --cc=bigeasy@linutronix.de \
    --cc=boqun.feng@gmail.com \
    --cc=chenzhongjin@huawei.com \
    --cc=f.fainelli@gmail.com \
    --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=tglx@linutronix.de \
    --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