On Fri, 2023-06-16 at 11:50 +0300, Mike Rapoport wrote: > From: "Mike Rapoport (IBM)" <rppt@xxxxxxxxxx> > > Hi, > > module_alloc() is used everywhere as a mean to allocate memory for > code. > > Beside being semantically wrong, this unnecessarily ties all > subsystmes > that need to allocate code, such as ftrace, kprobes and BPF to > modules and > puts the burden of code allocation to the modules code. > > Several architectures override module_alloc() because of various > constraints where the executable memory can be located and this > causes > additional obstacles for improvements of code allocation. I like how this series leaves the allocation code centralized at the end of it because it will be much easier when we get to ROX, huge page, text_poking() type stuff. I guess that's the idea. I'm just catching up on what you and Song have been up to.
