Re: [RFC PATCH 0/2] tracing - signal tracer, support multiple pidsin set_pid_ftrace

[Steven Rostedt]

On Mon, 2009-09-14 at 12:14 +0200, jolsa@xxxxxxxxxx wrote:
> I was debugging some ptrace applications and got to the idea of 
> tracing signals - signal tracer. There's probably possibility to 
> trace more info than just signal delivery info (like ignored 
> signals deliveries, queue status...).
> 
> While doing this I realized it might be worth to have ability to trace 
> more independent processes via set_pid_ftrace file.
> 
> Althought I'm sending this as RFC, attached patches work for me. 
> I'm open to any suggestions/comments/ideas.
> 
> 1/2 - signal trace

Don't make it a plugin. Just put the trace points into the signal
handler, and then you enable them via the event tracer.

> 2/2 - multiple pids support for set_pid_ftrace file

I took a quick look at this patch and I so far like it. But this will
not help you with events, but filtering will. That is:

 # echo "common_pid == 1234" > /debug/tracing/events/signals/signal/format

You can do multiple pids with "common_pid == 1234 || common_pid == 1235"

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/