On Tue, 19 Apr 2016 16:55:11 +0000 (UTC) Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx> wrote: > ----- On Apr 19, 2016, at 10:34 AM, rostedt rostedt@xxxxxxxxxxx wrote: > > > From: Steven Rostedt <rostedt@xxxxxxxxxxx> > > > > Add the infrastructure needed to have the PIDs in set_event_pid to > > automatically add PIDs of the children of the tasks that have their PIDs in > > set_event_pid. This will also remove PIDs from set_event_pid when a task > > exits > > > > This is implemented by adding hooks into the fork and exit tracepoints. On > > fork, the PIDs are added to the list, and on exit, they are removed. > > > > Add a new option called event_fork that when set, PIDs in set_event_pid will > > automatically get their children PIDs added when they fork, as well as any > > task that exits will have its PID removed from set_event_pid. > > Just out of curiosity: how does it deal with multi-process and multi-thread ? > What events are expected in each case ? > Not sure what you mean by that. This is in-kernel, and it's simply tasks. That is, any task (process or thread) that creates another task has its kernel pid checked. That would be the thread ID as well. So it works the same with processes as with threads because within the kernel they are just all just "tasks". -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-trace-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|