From: Joel Fernandes <joel@joelfernandes.org>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Daniel Colascione <dancol@google.com>,
"H. Peter Anvin" <hpa@zytor.com>, Pavel Machek <pavel@ucw.cz>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
ast@kernel.org, atish patra <atishp04@gmail.com>,
Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@redhat.com>,
Jan Kara <jack@suse.cz>, Jonathan Corbet <corbet@lwn.net>,
Karim Yaghmour <karim.yaghmour@opersys.com>,
Kees Cook <keescook@chromium.org>,
kernel-team@android.com,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Manoj Rao <linux@manojrajarao.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Randy Dunlap <rdunlap@infradead.org>,
rostedt@goodmis.org, Thomas Gleixner <tglx@linutronix.de>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>,
yhs@fb.com
Subject: Re: [RFC] Provide in-kernel headers for making it easy to extend the kernel
Date: Thu, 7 Mar 2019 18:12:07 -0500 [thread overview]
Message-ID: <20190307231207.GA51897@google.com> (raw)
In-Reply-To: <5e558126-9038-1ca5-4519-7b5864ca9fa1@metux.net>
Enrico,
On Thu, Mar 07, 2019 at 11:11:22PM +0100, Enrico Weigelt, metux IT consult wrote:
> On 07.03.19 21:55, Greg KH wrote:
>
> > Ick, no, no more squashfs please, let's just kill that mess once and for
> > all :)
>
> okay, then: s/squashfs/whatever_fs_image_or_archive_you_like/;
>
> > Again, putting this in a simple compressed tar image allows anyone to do
> > whatever they need to with this. If they want a full filesystem,
> > uncompress it and use it there. If they just want it in-memory where
> > they can uncompress it and then discard it, that works too.
>
> And let me stress the point: doesn't need any kernel changes at all,
> when it's just a file in the same place where the .ko's live.
Yes, but you're missing the point that some people would also opt to build it
into the kernel during their development/debugging (Config=y). For such
folks, they don't want to update the FS with anything during debug runs
either. Your "whole same place where the .ko lives" doesn't address Daniel's
usecase. You may say "initrd", but this is a much cleaner solution to that
IMO. There is no initrd needed and the path to the header files will be at a
standard location that is already pre-decided by the kernel.
As Greg said, you are welcome to keep it disabled for yourself if you don't
want it. This doesn't affect anyone else who doesn't use it.
next prev parent reply other threads:[~2019-03-07 23:12 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 22:55 [RFC] Provide in-kernel headers for making it easy to extend the kernel Joel Fernandes
2019-01-19 8:25 ` Greg KH
2019-01-19 16:27 ` Joel Fernandes
2019-01-19 17:43 ` Daniel Colascione
2019-01-19 23:25 ` Joel Fernandes
2019-01-19 23:44 ` hpa
2019-01-20 15:58 ` Joel Fernandes
2019-03-06 23:09 ` Pavel Machek
2019-03-06 23:37 ` Daniel Colascione
2019-03-07 0:07 ` H. Peter Anvin
2019-03-07 0:33 ` Daniel Colascione
2019-03-07 1:22 ` Enrico Weigelt, metux IT consult
2019-03-07 1:49 ` Daniel Colascione
2019-03-07 20:41 ` Enrico Weigelt, metux IT consult
2019-03-07 20:55 ` Greg KH
2019-03-07 22:11 ` Enrico Weigelt, metux IT consult
2019-03-07 23:12 ` Joel Fernandes [this message]
2019-03-07 23:40 ` hpa
2019-03-08 3:16 ` Joel Fernandes
2019-03-07 1:42 ` Joel Fernandes
2019-03-07 16:24 ` Enrico Weigelt, metux IT consult
2019-03-07 0:32 ` H. Peter Anvin
2019-03-07 0:36 ` Daniel Colascione
2019-03-07 0:42 ` Enrico Weigelt, metux IT consult
2019-03-07 1:48 ` Joel Fernandes
2019-03-07 17:37 ` Enrico Weigelt, metux IT consult
2019-01-19 8:26 ` Greg KH
2019-01-19 16:27 ` Joel Fernandes
2019-01-19 10:28 ` Christoph Hellwig
2019-01-19 10:36 ` Greg KH
2019-01-19 16:26 ` Joel Fernandes
2019-01-20 7:01 ` hpa
2019-01-20 16:10 ` Joel Fernandes
2019-01-20 21:58 ` hpa
2019-01-21 1:45 ` Joel Fernandes
2019-01-21 2:49 ` hpa
2019-01-21 4:38 ` Sandeep Patil
2019-01-22 13:39 ` Joel Fernandes
2019-01-23 21:29 ` Karim Yaghmour
2019-01-23 22:37 ` Daniel Colascione
2019-01-24 2:32 ` Joel Fernandes
2019-01-24 14:18 ` Joel Fernandes
2019-01-24 18:57 ` Karim Yaghmour
2019-01-24 20:59 ` Joel Fernandes
2019-01-25 19:00 ` hpa
2019-01-25 19:15 ` Daniel Colascione
2019-01-25 19:51 ` hpa
2019-01-25 20:34 ` Daniel Colascione
2019-01-25 20:46 ` Joel Fernandes
2019-01-25 20:28 ` Joel Fernandes
2019-03-06 23:09 ` Pavel Machek
2019-03-06 23:35 ` H. Peter Anvin
2019-01-26 12:05 Norbert Lange
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=20190307231207.GA51897@google.com \
--to=joel@joelfernandes.org \
--cc=akpm@linux-foundation.org \
--cc=ast@kernel.org \
--cc=atishp04@gmail.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dancol@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jack@suse.cz \
--cc=karim.yaghmour@opersys.com \
--cc=keescook@chromium.org \
--cc=kernel-team@android.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@manojrajarao.com \
--cc=lkml@metux.net \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.com \
--cc=yhs@fb.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).