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
WARNING: multiple messages have this Message-ID (diff)
From: joel at joelfernandes.org (Joel Fernandes)
Subject: [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
WARNING: multiple messages have this Message-ID (diff)
From: joel@joelfernandes.org (Joel Fernandes)
Subject: [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)
Message-ID: <20190325134947.jc5OM653vZ5XLi0UikMsZyeFiG1iJp51utwpwEc1zz4@z> (raw)
In-Reply-To: <20190215031926.ljzluy2cfxp64u6o@ast-mbp>
On Thu, Feb 14, 2019@07:19:29PM -0800, Alexei Starovoitov wrote:
> On Mon, Feb 11, 2019@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: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 14:35 [PATCH v2 1/2] Provide in-kernel headers for making it easy to extend the kernel Joel Fernandes (Google)
2019-02-11 14:35 ` Joel Fernandes (Google)
2019-02-11 14:35 ` joel
2019-02-11 14:36 ` [PATCH v2 2/2] Add selftests for module build using in-kernel headers Joel Fernandes (Google)
2019-02-11 14:36 ` Joel Fernandes (Google)
2019-02-11 14:36 ` joel
2019-02-13 22:50 ` [PATCH v2 1/2] Provide in-kernel headers for making it easy to extend the kernel Karim Yaghmour
2019-02-13 22:50 ` Karim Yaghmour
2019-02-13 22:50 ` karim.yaghmour
2019-02-15 3:19 ` Alexei Starovoitov
2019-02-15 3:19 ` Alexei Starovoitov
2019-02-15 3:19 ` alexei.starovoitov
2019-02-15 3:47 ` Joel Fernandes
2019-02-15 3:47 ` Joel Fernandes
2019-02-15 3:47 ` joel
2019-02-16 19:10 ` Manoj
2019-02-16 19:10 ` Manoj
2019-02-16 19:10 ` linux
2019-02-19 4:14 ` Masahiro Yamada
2019-02-19 4:14 ` Masahiro Yamada
2019-02-19 4:14 ` yamada.masahiro
2019-02-19 4:28 ` Alexei Starovoitov
2019-02-19 4:28 ` Alexei Starovoitov
2019-02-19 4:28 ` alexei.starovoitov
2019-02-19 4:34 ` Joel Fernandes
2019-02-19 4:34 ` Joel Fernandes
2019-02-19 4:34 ` joel
2019-02-19 4:42 ` Masahiro Yamada
2019-02-19 4:42 ` Masahiro Yamada
2019-02-19 4:42 ` yamada.masahiro
2019-02-19 5:12 ` Joel Fernandes
2019-02-19 5:12 ` Joel Fernandes
2019-02-19 5:12 ` joel
2019-02-19 15:16 ` Joel Fernandes
2019-02-19 15:16 ` Joel Fernandes
2019-02-19 15:16 ` joel
2019-02-21 14:34 ` Masahiro Yamada
2019-02-21 14:34 ` Masahiro Yamada
2019-02-21 14:34 ` yamada.masahiro
2019-02-21 15:29 ` Joel Fernandes
2019-02-21 15:29 ` Joel Fernandes
2019-02-21 15:29 ` joel
2019-03-25 13:49 ` Joel Fernandes [this message]
2019-03-25 13:49 ` Joel Fernandes
2019-03-25 13:49 ` joel
2019-03-27 17:31 ` Joel Fernandes
2019-03-27 17:31 ` Joel Fernandes
2019-03-27 17:31 ` joel
2019-04-03 7:48 ` Masahiro Yamada
2019-04-03 7:48 ` Masahiro Yamada
2019-04-03 7:48 ` yamada.masahiro
2019-04-03 17:20 ` Joel Fernandes
2019-04-03 17:20 ` Joel Fernandes
2019-04-03 17:20 ` joel
2019-04-03 17:46 ` Daniel Colascione
2019-04-03 17:46 ` Daniel Colascione
2019-04-03 17:46 ` dancol
2019-04-03 17:56 ` Joel Fernandes
2019-04-03 17:56 ` Joel Fernandes
2019-04-03 17:56 ` joel
2019-04-04 3:54 ` Masahiro Yamada
2019-04-04 3:54 ` Masahiro Yamada
2019-04-04 3:54 ` yamada.masahiro
-- strict thread matches above, loose matches on Subject: below --
2019-02-19 6:05 Alexey Dobriyan
2019-02-19 17:25 ` 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=20190325134947.GA187133@google.com \
--to=joel@joelfernandes.org \
--cc=akpm@linux-foundation.org \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=atishp04@gmail.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dancol@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=karim.yaghmour@opersys.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@manojrajarao.com \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--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 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.