[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221008154016.0f7ecd8f@rorschach.local.home>
Date: Sat, 8 Oct 2022 15:40:16 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Marcelo Tosatti <mtosatti@...hat.com>
Cc: Valentin Schneider <vschneid@...hat.com>,
linux-alpha@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-snps-arc@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-csky@...r.kernel.org,
linux-hexagon@...r.kernel.org, linux-ia64@...r.kernel.org,
loongarch@...ts.linux.dev, linux-mips@...r.kernel.org,
openrisc@...ts.librecores.org, linux-parisc@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, linux-riscv@...ts.infradead.org,
linux-s390@...r.kernel.org, linux-sh@...r.kernel.org,
sparclinux@...r.kernel.org, linux-xtensa@...ux-xtensa.org,
x86@...nel.org, "Paul E. McKenney" <paulmck@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Juri Lelli <juri.lelli@...hat.com>,
Daniel Bristot de Oliveira <bristot@...hat.com>,
Frederic Weisbecker <frederic@...nel.org>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>, Marc Zyngier <maz@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Russell King <linux@...linux.org.uk>,
Nicholas Piggin <npiggin@...il.com>,
Guo Ren <guoren@...nel.org>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [RFC PATCH 0/5] Generic IPI sending tracepoint
On Fri, 7 Oct 2022 17:01:33 -0300
Marcelo Tosatti <mtosatti@...hat.com> wrote:
> > As for the targeted CPUs, the existing tracepoint does export them, albeit in
> > cpumask form, which is quite inconvenient from a tooling perspective. For
> > instance, as far as I'm aware, it's not possible to do event filtering on a
> > cpumask via trace-cmd.
>
> https://man7.org/linux/man-pages/man1/trace-cmd-set.1.html
>
> -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.
We could always add an "isset(x)" filter ;-)
-- Steve
Powered by blists - more mailing lists