mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: jolsa@redhat.com
To: mingo@elte.hu, rostedt@goodmis.org
Cc: linux-kernel@vger.kernel.org
Subject: [RFC PATCH 0/2] tracing - signal tracer, support multiple pids in set_pid_ftrace
Date: Mon, 14 Sep 2009 12:14:09 +0200	[thread overview]
Message-ID: <1252923251-6735-1-git-send-email-jolsa@redhat.com> (raw)

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
2/2 - multiple pids support for set_pid_ftrace file

thanks,
jirka

Signed-off-by: Jiri Olsa <jolsa@redhat.com>
---
 include/linux/signaltrace.h |   22 ++++
 include/linux/tracehook.h   |   14 +++
 kernel/signal.c             |    3 +
 kernel/trace/Kconfig        |   11 ++
 kernel/trace/Makefile       |    1 +
 kernel/trace/ftrace.c       |  226 +++++++++++++++++++++++++++++++------------
 kernel/trace/trace.h        |   13 ++-
 kernel/trace/trace_signal.c |  132 +++++++++++++++++++++++++
 8 files changed, 356 insertions(+), 66 deletions(-)

             reply	other threads:[~2009-09-14 10:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-14 10:14 jolsa [this message]
2009-09-14 10:14 ` [RFC PATCH 1/2] tracing - signal tracer jolsa
2009-09-14 10:14 ` [RFC PATCH 2/2] tracing - support multiple pids in set_pid_ftrace file jolsa
2009-09-14 12:20 ` [RFC PATCH 0/2] tracing - signal tracer, support multiple pids in set_pid_ftrace Steven Rostedt
2009-09-14 13:59 ` Daniel Walker
2009-09-14 14:05   ` Jiri Olsa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1252923251-6735-1-git-send-email-jolsa@redhat.com \
    --to=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®