From: Willy Tarreau <w@1wt.eu>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
akiyks@gmail.com, bigeasy@linutronix.de, elver@google.com,
frederic@kernel.org, joel@joelfernandes.org, julia@ni.com,
mchehab+huawei@kernel.org, neeraju@codeaurora.org,
paul.gortmaker@windriver.com, peterz@infradead.org,
qiang.zhang@windriver.com, swood@redhat.com, urezki@gmail.com,
wangqing@vivo.com, linux-kernel@vger.kernel.org,
rcu@vger.kernel.org, kernel-team@fb.com, tglx@linutronix.de
Subject: Re: [GIT PULL tip/core/rcu] RCU, LKMM, and KCSAN commits for v5.12
Date: Sat, 13 Feb 2021 13:36:58 +0100 [thread overview]
Message-ID: <20210213123658.GA3500@1wt.eu> (raw)
In-Reply-To: <20210212150705.GO2743@paulmck-ThinkPad-P72>
Hi Paul,
On Fri, Feb 12, 2021 at 07:07:05AM -0800, Paul E. McKenney wrote:
> Thank you, Ingo! In the future, I will group nolibc with RCU. But there
> has to be something other than RCU that needs it. I will take a look. ;-)
All my kernels boot using a "preinit" that is built with nolibc and
integrated into the initramfs. Historically it used to just create /dev
entries and mount the rootfs, nowadays it's used to untar modules and
finish the boot so that I can have a clean separation between a kernel
image and a rootfs. It even allows to perform some minimal debugging as
it includes a minimalistic shell. Do you think something like this could
be of any use in your development sessions ? If so I can discuss this
with you in a separate thread so as not to annoy everyone. Just let me
know :-)
Cheers,
Willy
next prev parent reply other threads:[~2021-02-13 12:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 1:04 [GIT PULL tip/core/rcu] RCU, LKMM, and KCSAN commits for v5.12 Paul E. McKenney
2021-02-12 12:31 ` Ingo Molnar
2021-02-12 15:07 ` Paul E. McKenney
2021-02-13 12:36 ` Willy Tarreau [this message]
2021-02-13 16:44 ` "Single user mode" initrd [ Was: [GIT PULL tip/core/rcu] RCU, LKMM, and KCSAN commits for v5.12 ] Paul E. McKenney
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=20210213123658.GA3500@1wt.eu \
--to=w@1wt.eu \
--cc=akiyks@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=elver@google.com \
--cc=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=julia@ni.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mingo@kernel.org \
--cc=neeraju@codeaurora.org \
--cc=paul.gortmaker@windriver.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=qiang.zhang@windriver.com \
--cc=rcu@vger.kernel.org \
--cc=swood@redhat.com \
--cc=tglx@linutronix.de \
--cc=urezki@gmail.com \
--cc=wangqing@vivo.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).