From: Mark Rutland <mark.rutland@arm.com>
To: richard clark <richard.xnu.clark@gmail.com>
Cc: nico@fluxnic.net, Steven Rostedt <rostedt@goodmis.org>,
mhiramat@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Question about the ipi_raise filter usage and output
Date: Mon, 5 Feb 2024 10:28:57 +0000 [thread overview]
Message-ID: <ZcC4aWWKFU1NgrZM@FVFF77S0Q05N> (raw)
In-Reply-To: <CAJNi4rMpt88Gz+149wR9crzApmfUEfpS05sbOgAvOhzh2+Brbg@mail.gmail.com>
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:
> target_mask=00000000,00000bff (Function call interrupts)
> ...
> The above output is triggered by my kernel module where it will smp
> cross call a remote function from cpu#10 to cpu#11, for the
> 'target_mask' value, what does the '00000000,00000bff' mean?
That's a cpumask bitmap: 0xbff is 0b1011_1111_1111, which is:
,- CPU 10
|
1011_1111_1111
| '__________'
| |
| `- CPUs 9 to 0
|
`- CPU 11
Note that bitmap has CPUs 0-9 and CPU 11 set, but CPU 10 is not set.
I suspect your kernel module has generated the bitmap incorrectly; it looks
like you have a mask for CPUs 0-11 minus a mask for CPU 10?
For CPUs 10 and 11, that should be 0xc00 / 0b1100_0000_0000.
> ~~~~~~~~~~~~~~
>
> Another question is for the filter, I'd like to catch the IPI only
> happening on cpu#11 *AND* a remote function call, so how to write the
> 'target_cpus' in the filter expression?
>
> 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, the filter will skip the call.
I believe you can use '&' to check whether a cpumask contains a CPU, e.g.
'target_cpus & 11'
Thanks,
Mark.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-05 10:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 9:57 Question about the ipi_raise filter usage and output richard clark
2024-02-05 10:28 ` Mark Rutland [this message]
2024-02-05 13:06 ` Steven Rostedt
2024-02-05 14:39 ` Mark Rutland
2024-02-05 16:05 ` Valentin Schneider
2024-02-06 8:42 ` richard clark
2024-02-06 9:39 ` Valentin Schneider
2024-02-07 2:28 ` richard clark
2024-02-07 2:33 ` richard clark
2024-02-05 10:38 ` Steven Rostedt
2024-02-06 2:47 ` richard clark
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=ZcC4aWWKFU1NgrZM@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=nico@fluxnic.net \
--cc=richard.xnu.clark@gmail.com \
--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