All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <frederic@kernel.org>
To: "Joel Fernandes (Google)" <joel@joelfernandes.org>
Cc: linux-kernel@vger.kernel.org,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	linux-doc@vger.kernel.org,
	"Paul E. McKenney" <paulmck@kernel.org>,
	rcu@vger.kernel.org
Subject: Re: [PATCH RFC v2] rcu: Add a minimum time for marking boot as completed
Date: Sun, 26 Feb 2023 20:45:08 +0100	[thread overview]
Message-ID: <Y/u2xK8FHwKMsJNh@lothringen> (raw)
In-Reply-To: <20230225033421.3323164-1-joel@joelfernandes.org>

On Sat, Feb 25, 2023 at 03:34:21AM +0000, Joel Fernandes (Google) wrote:
> On many systems, a great deal of boot happens after the kernel thinks the boot
> has completed. It is difficult to determine if the system has really booted
> from the kernel side.

Is this only about kernel booting? What makes it hard to determine if the
system has really booted?

Thanks.

  parent reply	other threads:[~2023-02-26 19:45 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-25  3:34 [PATCH RFC v2] rcu: Add a minimum time for marking boot as completed Joel Fernandes (Google)
2023-02-25  3:36 ` Randy Dunlap
2023-02-25 11:55 ` kernel test robot
2023-02-26 19:45 ` Frederic Weisbecker [this message]
2023-02-26 23:07   ` Joel Fernandes
2023-02-27  7:53 ` Zhuo, Qiuxu
2023-02-27 13:22   ` Joel Fernandes
2023-02-27 14:55     ` Paul E. McKenney
2023-02-27 15:16       ` Joel Fernandes
2023-02-27 18:06         ` Uladzislau Rezki
2023-02-27 18:15           ` Joel Fernandes
2023-02-27 18:20             ` Uladzislau Rezki
2023-02-27 18:27               ` Joel Fernandes
2023-02-27 18:57                 ` Uladzislau Rezki
2023-02-27 19:10                   ` Joel Fernandes
2023-02-27 23:05                     ` Paul E. McKenney
2023-02-27 23:24                       ` Joel Fernandes
2023-02-27 23:40                       ` Frederic Weisbecker
2023-02-28  1:30                         ` Joel Fernandes
2023-02-28 11:04                           ` Frederic Weisbecker
2023-02-28 20:09                             ` Joel Fernandes
2023-03-01 17:11                               ` Frederic Weisbecker
2023-03-01 21:31                                 ` Joel Fernandes
2023-03-02  0:49                                   ` Paul E. McKenney
2023-03-02  1:08                                     ` Joel Fernandes
2023-03-02  1:19                                       ` Paul E. McKenney
2023-02-28 11:42                     ` Uladzislau Rezki
2023-02-28  6:40     ` Zhuo, Qiuxu
2023-02-28 14:27       ` Joel Fernandes
2023-03-01  1:34         ` Zhuo, Qiuxu
2023-03-01 15:57           ` Joel Fernandes

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=Y/u2xK8FHwKMsJNh@lothringen \
    --to=frederic@kernel.org \
    --cc=jiangshanlai@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=rcu@vger.kernel.org \
    /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.