Re: Question about the ipi_raise filter usage and output

On Wed, Feb 7, 2024 at 10:28 AM richard clark wrote: > > On Tue, Feb 6, 2024 at 5:39 PM Valentin Schneider wrote: > > > > You should have access to the generic fields which include the CPU from > > which the event happens. Any of "CPU", "cpu" or "common_cpu" would match > > this. > > > > So if

Re: Question about the ipi_raise filter usage and output

On Tue, Feb 6, 2024 at 5:39 PM Valentin Schneider wrote: > > You should have access to the generic fields which include the CPU from > which the event happens. Any of "CPU", "cpu" or "common_cpu" would match > this. > > So if you're on a recent enough kernel (v6.6 or above AFAICT), you should >

Re: Question about the ipi_raise filter usage and output

On 06/02/24 16:42, richard clark wrote: > On Tue, Feb 6, 2024 at 12:05 AM Valentin Schneider > wrote: >> >> The CPUS{} thingie only works with an event field that is either declared as >> a >> cpumask (__cpumask) or a scalar. That's not the case for ipi_raise, the >> target_cpus event field is

Re: Question about the ipi_raise filter usage and output

On Tue, Feb 6, 2024 at 12:05 AM Valentin Schneider wrote: > > On 05/02/24 14:39, Mark Rutland wrote: > > [adding Valentin] > > > > Thanks! > > > On Mon, Feb 05, 2024 at 08:06:09AM -0500, Steven Rostedt wrote: > >> On Mon, 5 Feb 2024 10:28:57 + > >> Mark Rutland wrote: > >> > >> > > I try to

Re: Question about the ipi_raise filter usage and output

Hi Steve, On Mon, Feb 5, 2024 at 6:38 PM Steven Rostedt wrote: > > On Mon, 5 Feb 2024 17:57:29 +0800 > richard clark wrote: > > > I try to write below: > > echo 'target_cpus == 11 && reason == "Function call interrupts"' > > > events/ipi/ipi_raise/filter > > You mean when it is sent only to CPU

Re: Question about the ipi_raise filter usage and output

On 05/02/24 14:39, Mark Rutland wrote: > [adding Valentin] > Thanks! > On Mon, Feb 05, 2024 at 08:06:09AM -0500, Steven Rostedt wrote: >> On Mon, 5 Feb 2024 10:28:57 + >> Mark Rutland wrote: >> >> > > I try to write below: >> > > echo 'target_cpus == 11 && reason == "Function call

Re: Question about the ipi_raise filter usage and output

[adding Valentin] On Mon, Feb 05, 2024 at 08:06:09AM -0500, Steven Rostedt wrote: > On Mon, 5 Feb 2024 10:28:57 + > Mark Rutland wrote: > > > > I try to write below: > > > echo 'target_cpus == 11 && reason == "Function call interrupts"' > > > > events/ipi/ipi_raise/filter > > > > The '='

Re: Question about the ipi_raise filter usage and output

On Mon, 5 Feb 2024 10:28:57 + Mark Rutland wrote: > > I try to write below: > > echo 'target_cpus == 11 && reason == "Function call interrupts"' > > > events/ipi/ipi_raise/filter > > The '=' checks if the target_cpus bitmap *only* contains CPU 11. If the > cpumask > contains other CPUs,

Re: Question about the ipi_raise filter usage and output

On Mon, 5 Feb 2024 17:57:29 +0800 richard clark wrote: > Hi guys, > > With the ipi_raise event enabled and filtered with: > echo 'reason == "Function call interrupts"' > filter, then the 'cat > trace' output below messages: > ... > insmod-3355[010] 1.. 24479.230381: ipi_raise: >

Re: Question about the ipi_raise filter usage and output

On Mon, Feb 05, 2024 at 05:57:29PM +0800, richard clark wrote: > Hi guys, > > With the ipi_raise event enabled and filtered with: > echo 'reason == "Function call interrupts"' > filter, then the 'cat > trace' output below messages: > ... > insmod-3355[010] 1.. 24479.230381: ipi_raise: >

Question about the ipi_raise filter usage and output

Hi guys, With the ipi_raise event enabled and filtered with: echo 'reason == "Function call interrupts"' > filter, then the 'cat trace' output below messages: ... insmod-3355[010] 1.. 24479.230381: ipi_raise: target_mask=,0bff (Function call interrupts) ... The above output is