On Tue, 14 Jul 2020 10:03:45 -0400
Steven Rostedt <rost...@goodmis.org> wrote:
> On Tue, 14 Jul 2020 14:33:14 +0100
> Mark Rutland <mark.rutl...@arm.com> wrote:
>
> > > Should work for all cases. Yes, we might then want something like a per
> > > arch:
> > >
> > > {BPF,FTRACE,KPROBE}_TEXT_TYPE
> >
> > ... at that point why not:
> >
> > text_alloc_ftrace();
> > text_alloc_module();
> > text_alloc_bpf();
> > text_alloc_kprobe();
>
> I don't know about bpf and kprobes, but for ftrace, the only place that
> it allocates text happens to be in arch specific code.
>
> If you want something special for ftrace, you could just add your own
> function. But for x86, a text_alloc_immediate() would work.
> (BTW, I like the function names over the enums)
kprobes will need the text_alloc_immediate() too, since it will use
the trampoline buffer where jumps to/from kernel code/modules.
Thanks,
--
Masami Hiramatsu <mhira...@kernel.org>
