• Steven Rostedt (Google)'s avatar
    ftrace: Add subops logic to allow one ops to manage many · 5fccc755
    Steven Rostedt (Google) authored
    There are cases where a single system will use a single function callback
    to handle multiple users. For example, to allow function_graph tracer to
    have multiple users where each can trace their own set of functions, it is
    useful to only have one ftrace_ops registered to ftrace that will call a
    function by the function_graph tracer to handle the multiplexing with the
    different registered  function_graph tracers.
    
    Add a "subop_list" to the ftrace_ops that will hold a list of other
    ftrace_ops that the top ftrace_ops will manage.
    
    The function ftrace_startup_subops() that takes the manager ftrace_ops and
    a subop ftrace_ops it will manage. If there are no subops with the
    ftrace_ops yet, it will copy the ftrace_ops subop filters to the manager
    ftrace_ops and register that with ftrace_startup(), and adds the subop to
    its subop_list. If the manager ops already has something registered, it
    will then merge the new subop filters with what it has and enable the new
    functions that covers all the subops it has.
    
    To remove a subop, ftrace_shutdown_subops() is called which will use the
    subop_list of the manager ops to rebuild all the functions it needs to
    trace, and update the ftrace records to only call the functions it now has
    registered. If there are no more functions registered, it will then call
    ftrace_shutdown() to disable itself completely.
    
    Note, it is up to the manager ops callback to always make sure that the
    subops callbacks are called if its filter matches, as there are times in
    the update where the callback could be calling more functions than those
    that are currently registered.
    
    This could be updated to handle other systems other than function_graph,
    for example, fprobes could use this (but will need an interface to call
    ftrace_startup_subops()).
    
    Link: https://lore.kernel.org/linux-trace-kernel/20240603190822.508431129@goodmis.org
    
    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: Mark Rutland <mark.rutland@arm.com>
    Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
    Cc: Andrew Morton <akpm@linux-foundation.org>
    Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>
    Cc: Florent Revest <revest@chromium.org>
    Cc: Martin KaFai Lau <martin.lau@linux.dev>
    Cc: bpf <bpf@vger.kernel.org>
    Cc: Sven Schnelle <svens@linux.ibm.com>
    Cc: Alexei Starovoitov <ast@kernel.org>
    Cc: Jiri Olsa <jolsa@kernel.org>
    Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
    Cc: Daniel Borkmann <daniel@iogearbox.net>
    Cc: Alan Maguire <alan.maguire@oracle.com>
    Cc: Peter Zijlstra <peterz@infradead.org>
    Cc: Thomas Gleixner <tglx@linutronix.de>
    Cc: Guo Ren <guoren@kernel.org>
    Reviewed-by: default avatarMasami Hiramatsu (Google) <mhiramat@kernel.org>
    Signed-off-by: default avatarSteven Rostedt (Google) <rostedt@goodmis.org>
    5fccc755
trace.h 67 KB