[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51C2B8AB.8060709@broadcom.com>
Date: Thu, 20 Jun 2013 10:09:15 +0200
From: "Arend van Spriel" <arend@...adcom.com>
To: "Steven Rostedt" <rostedt@...dmis.org>
cc: linux-kernel@...r.kernel.org, "Ingo Molnar" <mingo@...nel.org>,
"Frederic Weisbecker" <fweisbec@...il.com>,
"Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: [for-next][PATCH 08/12] tracing: Add binary & filter for
events
On 06/20/2013 05:35 AM, Steven Rostedt wrote:
> By allowing a binary '&' operation, this gives the user the ability to
> test a bit.
>
> Note, a binary '|' is not added, as it doesn't make sense as fields must
> be compared to constants (for now), and ORing a constant will always return
> true.
>
> Link:http://lkml.kernel.org/r/1371057385.9844.261.camel@gandalf.local.home
>
> Suggested-by: Arend van Spriel<arend@...adcom.com>
Actually, my attempt was triggered by the trace-cmd manual page:
"-f filter
Specify a filter for the previous event. This must come after a -e. This
will filter what events get recorded based on the content of the event.
Filtering is passed to the kernel directly so what filtering is allowed
may depend on what version of the kernel you have. Basically, it will
let you use C notation to check if an event should be processed or not.
==, >=, <=, >, <, &, |, && and ||
The above are usually safe to use to compare fields."
> Tested-by: Arend van Spriel<arend@...adcom.com>
> Signed-off-by: Steven Rostedt<rostedt@...dmis.org>
Regards,
Arend
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists