MIME-Version: 1.0
References: <20230225033421.3323164-1-joel@joelfernandes.org> <Y/u2xK8FHwKMsJNh@lothringen>
In-Reply-To: <Y/u2xK8FHwKMsJNh@lothringen>
From:   Joel Fernandes <joel@joelfernandes.org>
Date:   Sun, 26 Feb 2023 18:07:26 -0500
Message-ID: <CAEXW_YT7v42_AcJfOKDxbXoWxfMkfK1-sU8E=nMiSZTk0b2krA@mail.gmail.com>
Subject: Re: [PATCH RFC v2] rcu: Add a minimum time for marking boot as completed
To:     Frederic Weisbecker <frederic@kernel.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
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Sun, Feb 26, 2023 at 2:45=E2=80=AFPM Frederic Weisbecker <frederic@kerne=
l.org> wrote:
>
> 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 t=
he boot
> > has completed. It is difficult to determine if the system has really bo=
oted
> > from the kernel side.
>
> Is this only about kernel booting? What makes it hard to determine if the
> system has really booted?

Yes, I should probably clarify in the change log. It is more than the
kernel booting, it is all OS userspace code that runs as well during
which the CPU load is high (init spawning new programs such as shells,
daemons setup etc). The kernel does not know when that will complete
per-se. A timer based approach is not ideal, but it does not hurt
either IMHO. In other words, it is a "something better than nothing"
patch which reduces risk of slowness.


Thanks,

 - Joel