From: Steven Rostedt <rostedt@goodmis.org>
To: Daniel Wagner <daniel.wagner@bmw-carit.de>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH v0] tracing: Allow triggers to filter for CPU ids and process names
Date: Tue, 11 Aug 2015 18:28:08 -0400 [thread overview]
Message-ID: <20150811182808.75c9cf0f@gandalf.local.home> (raw)
In-Reply-To: <1439210146-24707-1-git-send-email-daniel.wagner@bmw-carit.de>
On Mon, 10 Aug 2015 14:35:46 +0200
Daniel Wagner <daniel.wagner@bmw-carit.de> wrote:
> By extending the filter rules by more generic fields
> we can write triggers filters like
>
> echo 'stacktrace if cpu == 1' > \
> /sys/kernel/debug/tracing/events/raw_syscalls/sys_enter/trigger
>
> or
>
> echo 'stacktrace if comm == sshd' > \
> /sys/kernel/debug/tracing/events/raw_syscalls/sys_enter/trigger
>
> CPU and COMM are not part of struct trace_entry. We could add the two
> new fields to ftrace_common_field list and fix up all depending
> sides. But that looks pretty ugly. Another thing I would like to
> avoid that the 'format' file contents changes.
>
> All this can be avoided by introducing another list which contains
> non field members of struct trace_entry.
>
> Signed-off-by: Daniel Wagner <daniel.wagner@bmw-carit.de>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: linux-kernel@vger.kernel.org
v0? Expect more revisions? ;-)
Looks fine. I pulled it into my queue.
-- Steve
prev parent reply other threads:[~2015-08-11 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 12:35 Daniel Wagner
2015-08-11 22:28 ` Steven Rostedt [this message]
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=20150811182808.75c9cf0f@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=daniel.wagner@bmw-carit.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
/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®