Skip to content
Snippets Groups Projects
  • Steven Rostedt (VMware)'s avatar
    7b60f3d8
    ftrace: Dynamically create the probe ftrace_ops for the trace_array · 7b60f3d8
    Steven Rostedt (VMware) authored
    
    In order to eventually have each trace_array instance have its own unique
    set of function probes (triggers), the trace array needs to hold the ops and
    the filters for the probes.
    
    This is the first step to accomplish this. Instead of having the private
    data of the probe ops point to the trace_array, create a separate list that
    the trace_array holds. There's only one private_data for a probe, we need
    one per trace_array. The probe ftrace_ops will be dynamically created for
    each instance, instead of being static.
    
    Signed-off-by: default avatarSteven Rostedt (VMware) <rostedt@goodmis.org>
    7b60f3d8
    History
    ftrace: Dynamically create the probe ftrace_ops for the trace_array
    Steven Rostedt (VMware) authored
    
    In order to eventually have each trace_array instance have its own unique
    set of function probes (triggers), the trace array needs to hold the ops and
    the filters for the probes.
    
    This is the first step to accomplish this. Instead of having the private
    data of the probe ops point to the trace_array, create a separate list that
    the trace_array holds. There's only one private_data for a probe, we need
    one per trace_array. The probe ftrace_ops will be dynamically created for
    each instance, instead of being static.
    
    Signed-off-by: default avatarSteven Rostedt (VMware) <rostedt@goodmis.org>
Code owners
Assign users and groups as approvers for specific file changes. Learn more.