Searched refs:onmatch (Results 1 – 2 of 2) sorted by relevance
334 } onmatch; member1001 struct synth_event *event = data->onmatch.synth_event; in action_trace()1003 trace_synth(event, var_ref_vals, data->onmatch.var_ref_idx); in action_trace()1573 char *system = data->onmatch.match_event_system; in find_match_var()1574 char *event_name = data->onmatch.match_event; in find_match_var()3496 kfree(data->onmatch.match_event); in onmatch_destroy()3497 kfree(data->onmatch.match_event_system); in onmatch_destroy()3498 kfree(data->onmatch.synth_event_name); in onmatch_destroy()3503 if (data->onmatch.synth_event) in onmatch_destroy()3504 data->onmatch.synth_event->ref--; in onmatch_destroy()[all …]
1817 how that is done using hist trigger 'onmatch' action). Once that is1850 - onmatch(matching.event).<synthetic_event_name>(param list)1852 The 'onmatch(matching.event).<synthetic_event_name>(params)' hist1872 onmatch() functionality, in the form 'system.event_name'.1890 variable and specifies an onmatch() action that generates a1895 # echo 'hist:keys=$testpid:testpid=pid:onmatch(sched.sched_wakeup_new).\1934 onmatch(sched.sched_waking).wakeup_latency($wakeup_lat,\2033 …# echo 'hist:keys=common_pid:lat=common_timestamp.usecs-$ts0:onmatch(ftrace.print).latency($lat) i…2364 …# echo 'hist:keys=common_pid:lat=common_timestamp.usecs-$ts0:onmatch(sched.sched_waking).latency($…