From: Joel Fernandes <joel@joelfernandes•org>
To: Alexei Starovoitov <alexei.starovoitov@gmail•com>
Cc: netdev@vger•kernel.org, linux-kernel@vger•kernel.org,
Andrew Morton <akpm@linux-foundation•org>,
ast@kernel•org, atishp04@gmail•com, dancol@google•com,
Dan Williams <dan.j.williams@intel•com>,
gregkh@linuxfoundation•org, Jonathan Corbet <corbet@lwn•net>,
karim.yaghmour@opersys•com, Kees Cook <keescook@chromium•org>,
linux-doc@vger•kernel.org, linux-kselftest@vger•kernel.org,
Manoj Rao <linux@manojrajarao•com>,
Masahiro Yamada <yamada.masahiro@socionext•com>,
paulmck@linux•vnet.ibm.com,
"Peter Zijlstra (Intel)" <peterz@infradead•org>,
rdunlap@infradead•org, rostedt@goodmis•org,
Shuah Khan <shuah@kernel•org>,
Thomas Gleixner <tglx@linutronix•de>,
yhs@fb•com
Subject: Re: [PATCH v2 1/2] Provide in-kernel headers for making it easy to extend the kernel
Date: Mon, 25 Mar 2019 09:49:47 -0400 [thread overview]
Message-ID: <20190325134947.GA187133@google.com> (raw)
In-Reply-To: <20190215031926.ljzluy2cfxp64u6o@ast-mbp>
On Thu, Feb 14, 2019 at 07:19:29PM -0800, Alexei Starovoitov wrote:
> On Mon, Feb 11, 2019 at 09:35:59AM -0500, Joel Fernandes (Google) wrote:
> > Introduce in-kernel headers and other artifacts which are made available
> > as an archive through proc (/proc/kheaders.txz file). This archive makes
> > it possible to build kernel modules, run eBPF programs, and other
> > tracing programs that need to extend the kernel for tracing purposes
> > without any dependency on the file system having headers and build
> > artifacts.
> >
> > On Android and embedded systems, it is common to switch kernels but not
> > have kernel headers available on the file system. Raw kernel headers
> > also cannot be copied into the filesystem like they can be on other
> > distros, due to licensing and other issues. There's no linux-headers
> > package on Android. Further once a different kernel is booted, any
> > headers stored on the file system will no longer be useful. By storing
> > the headers as a compressed archive within the kernel, we can avoid these
> > issues that have been a hindrance for a long time.
>
> The set looks good to me and since the main use case is building bpf progs
> I can route it via bpf-next tree if there are no objections.
> Masahiro, could you please ack it?
FYI, Masahiro's comments were all address by v5:
https://lore.kernel.org/patchwork/project/lkml/list/?series=387311
I believe aren't more outstanding concerns. Could we consider it for v5.2?
thanks,
- Joel
next prev parent reply other threads:[~2019-03-25 13:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190211143600.15021-1-joel@joelfernandes.org>
2019-02-15 3:19 ` [PATCH v2 1/2] Provide in-kernel headers for making it easy to extend the kernel Alexei Starovoitov
2019-02-15 3:47 ` Joel Fernandes
2019-02-16 19:10 ` Manoj
2019-02-19 4:14 ` Masahiro Yamada
2019-02-19 4:28 ` Alexei Starovoitov
2019-02-19 4:34 ` Joel Fernandes
2019-02-19 4:42 ` Masahiro Yamada
2019-02-19 5:12 ` Joel Fernandes
2019-02-19 15:16 ` Joel Fernandes
2019-02-21 14:34 ` Masahiro Yamada
2019-02-21 15:29 ` Joel Fernandes
2019-03-25 13:49 ` Joel Fernandes [this message]
2019-03-27 17:31 ` Joel Fernandes
2019-04-03 7:48 ` Masahiro Yamada
2019-04-03 17:20 ` Joel Fernandes
2019-04-03 17:46 ` Daniel Colascione
2019-04-03 17:56 ` Joel Fernandes
2019-04-04 3:54 ` Masahiro Yamada
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=20190325134947.GA187133@google.com \
--to=joel@joelfernandes$(echo .)org \
--cc=akpm@linux-foundation$(echo .)org \
--cc=alexei.starovoitov@gmail$(echo .)com \
--cc=ast@kernel$(echo .)org \
--cc=atishp04@gmail$(echo .)com \
--cc=corbet@lwn$(echo .)net \
--cc=dan.j.williams@intel$(echo .)com \
--cc=dancol@google$(echo .)com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=karim.yaghmour@opersys$(echo .)com \
--cc=keescook@chromium$(echo .)org \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-kselftest@vger$(echo .)kernel.org \
--cc=linux@manojrajarao$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=paulmck@linux$(echo .)vnet.ibm.com \
--cc=peterz@infradead$(echo .)org \
--cc=rdunlap@infradead$(echo .)org \
--cc=rostedt@goodmis$(echo .)org \
--cc=shuah@kernel$(echo .)org \
--cc=tglx@linutronix$(echo .)de \
--cc=yamada.masahiro@socionext$(echo .)com \
--cc=yhs@fb$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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