Especially if you call this "get" rather than "deliver", there is
another place that should invoke this tracepoint (or perhaps a third
one). sys_rt_sigtimedwait "gets" a signal without delivering it. In
POSIX terminology this is called "accepting" the signal: the three
things that can happen in the life of a signal are "generate",
"deliver", and "accept". If you are trying to match up what happened
to a signal generated by kill() or whatnot, then you want to notice
both delivery and acceptance as the complementary event.
(And again I have no clue why this signal stuff should be called
"sched" at all.)
it shouldnt be called 'sched' - it should go into 'events/signal.h'.
But we also need fuller coverage than this. Coredumps and signal
delivery events are just a small part of all things signals, we also
want:
- signal generation events (send_sig*() variants)
- signal IPI/wakeup events
- signal loss events (queue overflow)