linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH 2/2] trace-cmd: Print configured filtered PIDs in trace-cmd stat command
Date: Tue, 21 Apr 2020 13:47:13 +0300	[thread overview]
Message-ID: <20200421104713.31762-3-tz.stoyanov@gmail.com> (raw)
In-Reply-To: <20200421104713.31762-1-tz.stoyanov@gmail.com>

Print information of currently configured filtered event PIDs and
filtered function tracer PIDs in trace-cmd stat command. This information
is part of the ftrace configuration and should be displayed by the stat command.

Signed-off-by: Tzvetomir Stoyanov (VMware) <tz.stoyanov@gmail.com>
---
 tracecmd/trace-stat.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/tracecmd/trace-stat.c b/tracecmd/trace-stat.c
index 2e3d83c3..e9369842 100644
--- a/tracecmd/trace-stat.c
+++ b/tracecmd/trace-stat.c
@@ -900,6 +900,9 @@ static void stat_instance(struct buffer_instance *instance)
 	report_file(instance, "tracing_max_latency", "0", "Max Latency: ");
 	report_kprobes(instance);
 	report_uprobes(instance);
+	report_file(instance, "set_event_pid", "", "Filtered event PIDs:\n");
+	report_file(instance, "set_ftrace_pid", "no pid",
+		    "Filtered function tracer PIDs:\n");
 	report_traceon(instance);
 	report_file(instance, "error_log", "", "Error log:\n");
 }
-- 
2.25.3


      parent reply	other threads:[~2020-04-21 10:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 10:47 [PATCH 0/2] Display more ftrace configuration by trace-cmd stat Tzvetomir Stoyanov (VMware)
2020-04-21 10:47 ` [PATCH 1/2] trace-cmd: Add helper function to print content of a trace file Tzvetomir Stoyanov (VMware)
2020-07-02 18:10   ` Steven Rostedt
2020-04-21 10:47 ` Tzvetomir Stoyanov (VMware) [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=20200421104713.31762-3-tz.stoyanov@gmail.com \
    --to=tz.stoyanov@gmail.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).