From: Omar Sandoval <osandov@osandov.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Namhyung Kim <namhyung@gmail.com>
Cc: linux-kernel@vger.kernel.org, kernel-team@fb.com,
Omar Sandoval <osandov@fb.com>
Subject: [PATCH v2 0/3] tracing: expose current->comm to [ku]probe events
Date: Thu, 2 Jun 2016 18:11:00 -0700 [thread overview]
Message-ID: <cover.1464916142.git.osandov@fb.com> (raw)
From: Omar Sandoval <osandov@fb.com>
Hi,
Respinning with a few changes:
- Added patches 1 and 3 (document "string_size" type and make "string"
default for $comm)
- Also support uprobe events
- Only allow "string" and "string_size" types
Patch 2, which actually introduces $comm, is pretty simple. Patch 3 is
more intrusive, but without it, the default type for $comm is invalid,
which is stupid.
This series applies to v4.7-rc1.
Thanks!
Omar Sandoval (3):
tracing: document "string_size" [ku]probe type
tracing: expose current->comm to [ku]probe events
tracing: make "string" the default type for [ku]probe event $comm
Documentation/trace/kprobetrace.txt | 15 +++--
Documentation/trace/uprobetracer.txt | 13 ++--
kernel/trace/trace_kprobe.c | 1 +
kernel/trace/trace_probe.c | 123 ++++++++++++++++++++++++++---------
kernel/trace/trace_probe.h | 10 +++
5 files changed, 123 insertions(+), 39 deletions(-)
--
2.8.3
next reply other threads:[~2016-06-03 1:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 1:11 Omar Sandoval [this message]
2016-06-03 1:11 ` [PATCH v2 1/3] tracing: document "string_size" [ku]probe type Omar Sandoval
2016-06-07 6:29 ` Masami Hiramatsu
2016-06-03 1:11 ` [PATCH v2 2/3] tracing: expose current->comm to [ku]probe events Omar Sandoval
2016-06-07 7:24 ` Masami Hiramatsu
2016-06-07 13:40 ` Namhyung Kim
2016-06-03 1:11 ` [PATCH v2 3/3] tracing: make "string" the default type for [ku]probe event $comm Omar Sandoval
2016-06-07 8:02 ` Masami Hiramatsu
2016-06-07 13:41 ` Namhyung Kim
2016-06-08 13:43 ` Steven Rostedt
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=cover.1464916142.git.osandov@fb.com \
--to=osandov@osandov.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@gmail.com \
--cc=osandov@fb.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.