linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gabriel Krisman Bertazi <krisman@suse.de>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org,
	Gabriel Krisman Bertazi <krisman@suse.de>
Subject: [PATCH trace-cmd v2 2/3] trace-cmd-report: Support global filters
Date: Thu, 30 Mar 2023 15:52:10 -0300	[thread overview]
Message-ID: <20230330185211.5604-3-krisman@suse.de> (raw)
In-Reply-To: <20230330185211.5604-1-krisman@suse.de>

When a filter is provided before an input file, consider it globally
applying to all traces:

i.e., the following will trace kernel_stack out of both traces instead
of only the first:

  $ trace-cmd report -v -F kernel_stack -i trace1.dat -i trace2.dat

Filter order matters due to the order of processing. Always process
global filters first, which are likely more generic.

Signed-off-by: Gabriel Krisman Bertazi <krisman@suse.de>
---
 tracecmd/trace-read.c | 42 ++++++++++++++++++++++++++----------------
 1 file changed, 26 insertions(+), 16 deletions(-)

diff --git a/tracecmd/trace-read.c b/tracecmd/trace-read.c
index 6a872d7..f645c05 100644
--- a/tracecmd/trace-read.c
+++ b/tracecmd/trace-read.c
@@ -562,30 +562,40 @@ static void make_pid_filter(struct tracecmd_input *handle,
 	}
 }
 
+static int __process_filters(struct tracecmd_input *handle,
+			     struct filter_str *filters)
+{
+	struct tracecmd_filter *trace_filter;
+
+	for (; filters; filters = filters->next) {
+		trace_filter = tracecmd_filter_add(handle,
+						   filters->filter,
+						   filters->neg);
+		if (!trace_filter)
+			die("Failed to create event filter: %s",
+			    filters->filter);
+	}
+
+	return !!filters;
+}
+
 static void process_filters(struct handle_list *handles)
 {
 	struct input_files *input_file = handles->input_file ?: last_input_file;
-	struct tracecmd_filter *trace_filter;
-	struct filter_str *filter;
-	int filters = 0;
+	int added = 0;
 
 	make_pid_filter(handles->handle, input_file);
 
+	/*
+	 * Order of filter processing matters. Apply the global filters
+	 * before file-specific ones.
+	 */
+	added += __process_filters(handles->handle, filter_strings);
 	if (input_file)
-		filter = input_file->filter_str;
-	else
-		filter = filter_strings;
-
-	for (; filter; filter = filter->next) {
-		trace_filter = tracecmd_filter_add(handles->handle,
-						   filter->filter,
-						   filter->neg);
-		if (!trace_filter)
-			die("Failed to create event filter: %s", filter->filter);
+		added += __process_filters(handles->handle,
+					   input_file->filter_str);
 
-		filters++;
-	}
-	if (filters && test_filters_mode)
+	if (added && test_filters_mode)
 		exit(0);
 }
 
-- 
2.40.0


  parent reply	other threads:[~2023-03-30 18:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 18:52 [PATCH trace-cmd v2 0/3] trace-cmd filtering Gabriel Krisman Bertazi
2023-03-30 18:52 ` [PATCH trace-cmd v2 1/3] trace-cmd report: Ensure filter is applied to single input file Gabriel Krisman Bertazi
2023-03-30 18:52 ` Gabriel Krisman Bertazi [this message]
2023-03-30 18:52 ` [PATCH trace-cmd v2 3/3] documentation: trace-cmd-report: Document filter scope Gabriel Krisman Bertazi
2023-05-06 22:35 ` [PATCH trace-cmd v2 0/3] trace-cmd filtering Gabriel Krisman Bertazi
2023-05-07  1:51   ` Steven Rostedt
2023-05-30  8:20 ` 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=20230330185211.5604-3-krisman@suse.de \
    --to=krisman@suse.de \
    --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).