From: Sebastian Andrzej Siewior <firstname.lastname@example.org>
To: "Paul E. McKenney" <email@example.com>
Cc: Thomas Gleixner <firstname.lastname@example.org>,
"tip-bot2 for Paul E. McKenney" <email@example.com>,
Uladzislau Rezki <firstname.lastname@example.org>,
Peter Zijlstra <email@example.com>,
Frederic Weisbecker <firstname.lastname@example.org>,
Subject: Re: [tip: core/rcu] softirq: Don't try waking ksoftirqd before it has been spawned
Date: Wed, 14 Apr 2021 09:13:22 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
On 2021-04-12 11:36:45 [-0700], Paul E. McKenney wrote:
> > Color me confused. I did not follow the discussion around this
> > completely, but wasn't it agreed on that this rcu torture muck can wait
> > until the threads are brought up?
> Yes, we can cause rcutorture to wait. But in this case, rcutorture
> is just the messenger, and making it wait would simply be ignoring
> the message. The message is that someone could invoke any number of
> things that wait on a softirq handler's invocation during the interval
> before ksoftirqd has been spawned.
My memory on this is that the only user, that required this early
behaviour, was kprobe which was recently changed to not need it anymore.
Which makes the test as the only user that remains. Therefore I thought
that this test will be moved to later position (when ksoftirqd is up and
running) and that there is no more requirement for RCU to be completely
up that early in the boot process.
Did I miss anything?
> Thanx, Paul
next prev parent reply other threads:[~2021-04-14 7:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-11 13:43 [tip: core/rcu] softirq: Don't try waking ksoftirqd before it has been spawned tip-bot2 for Paul E. McKenney
2021-04-12 14:16 ` Thomas Gleixner
2021-04-12 18:36 ` Paul E. McKenney
2021-04-14 7:13 ` Sebastian Andrzej Siewior [this message]
2021-04-14 8:57 ` Uladzislau Rezki
2021-04-14 18:11 ` Paul E. McKenney
2021-04-14 23:54 ` Thomas Gleixner
2021-04-15 5:02 ` Paul E. McKenney
2021-04-15 14:34 ` Uladzislau Rezki
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).