On Wed, 17 Apr 2019 10:25:15 -0400 Phil Auld <pauld@xxxxxxxxxx> wrote: > > > FILTER write /sys/kernel/debug/tracing/events/sched/sched_kthread_stop/filter (len 74) value "(common_pid<21420||common_pid>21425)&&(common_pid<21265||common_pid>21418)" > > > FILTER write /sys/kernel/debug/tracing/events/sched/sched_kthread_stop_ret/filter (len 74) value "(common_pid<21420||common_pid>21425)&&(common_pid<21265||common_pid>21418)" > > > ... > > > FILTER write /sys/kernel/debug/tracing/events/sched/sched_switch/filter (len 142) value "(common_pid<21420||common_pid>21425)&&(common_pid<21265||common_pid>21418)||(next_pid<21420||next_pid>21425)&&(next_pid<21265||next_pid>21418)" > > > > It seems crazy that we write "common_pid", instead of "pid" or "cpid", or > > something like that. > > > > > > > > I assume those have to match fields in the trace event mechanism, but I don't know a lot > about it. > > "pid" is used in the wakeup event filters: > > FILTER write /sys/kernel/debug/tracing/events/sched/sched_wakeup_new/filter (len 122) value "(common_pid<21420||common_pid>21425)&&(common_pid<21265||common_pid>21418)||(pid<21420||pid>21425)&&(pid<21265||pid>21418)" > Correct, the names have to match the fields listed in the format file. The "common_*" was added way back in the beginning so that they differ from the field names in the events. -- Steve
|