Messages in this thread | | | Date | Tue, 20 Jun 2023 10:51:04 -0400 | From | Steven Rostedt <> | Subject | Re: [PATCH v2 06/12] mm/execmem: introduce execmem_data_alloc() |
| |
On Mon, 19 Jun 2023 02:43:58 +0200 Thomas Gleixner <tglx@linutronix.de> wrote:
> Now you might argue that it _is_ a "hotpath" due to the BPF usage, but > then even more so as any intermediate wrapper which converts from one > data representation to another data representation is not going to > increase performance, right?
Just as a side note. BPF can not attach its return calling code to functions that have more than 6 parameters (3 on 32 bit x86), because of the way BPF return path trampoline works. It is a requirement that all parameters live in registers, and none on the stack.
-- Steve
| |