[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240308114542.6eafe78de8969ba33affd41d@kernel.org>
Date: Fri, 8 Mar 2024 11:45:42 +0900
From: Masami Hiramatsu (Google) <mhiramat@...nel.org>
To: Luis Chamberlain <mcgrof@...nel.org>
Cc: Calvin Owens <jcalvinowens@...il.com>, Song Liu <song@...nel.org>,
Christophe Leroy <christophe.leroy@...roup.eu>, Mike Rapoport
<rppt@...nel.org>, Andrew Morton <akpm@...ux-foundation.org>, Alexei
Starovoitov <ast@...nel.org>, Steven Rostedt <rostedt@...dmis.org>, Daniel
Borkmann <daniel@...earbox.net>, Andrii Nakryiko <andrii@...nel.org>,
Masami Hiramatsu <mhiramat@...nel.org>, Naveen N Rao
<naveen.n.rao@...ux.ibm.com>, Anil S Keshavamurthy
<anil.s.keshavamurthy@...el.com>, David S Miller <davem@...emloft.net>,
Thomas Gleixner <tglx@...utronix.de>, bpf@...r.kernel.org,
linux-modules@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH 0/4] Make bpf_jit and kprobes work with
CONFIG_MODULES=n
Hi,
On Wed, 6 Mar 2024 13:34:40 -0800
Luis Chamberlain <mcgrof@...nel.org> wrote:
> On Wed, Mar 06, 2024 at 12:05:07PM -0800, Calvin Owens wrote:
> > Hello all,
> >
> > This patchset makes it possible to use bpftrace with kprobes on kernels
> > built without loadable module support.
>
> This is a step in the right direction for another reason: clearly the
> module_alloc() is not about modules, and we have special reasons for it
> now beyond modules. The effort to share a generalize a huge page for
> these things is also another reason for some of this but that is more
> long term.
Indeed. If it works without CONFIG_MODULES, it may be exec_alloc() or
something like that. Anyway, thanks for great job on this item!
>
> I'm all for minor changes here so to avoid regressions but it seems a
> rename is in order -- if we're going to all this might as well do it
> now. And for that I'd just like to ask you paint the bikeshed with
> Song Liu as he's been the one slowly making way to help us get there
> with the "module: replace module_layout with module_memory",
> and Mike Rapoport as he's had some follow up attempts [0]. As I see it,
> the EXECMEM stuff would be what we use instead then. Mike kept the
> module_alloc() and the execmem was just a wrapper but your move of the
> arch stuff makes sense as well and I think would complement his series
> nicely.
yeah, it is better to work with Mike.
Thank you,
>
> If you're gonna split code up to move to another place, it'd be nice
> if you can add copyright headers as was done with the kernel/module.c
> split into kernel/module/*.c
>
> Can we start with some small basic stuff we can all agree on?
>
> [0] https://lwn.net/Articles/944857/
>
> Luis
--
Masami Hiramatsu (Google) <mhiramat@...nel.org>
Powered by blists - more mailing lists