linux-kernel - Re: Will smp_call_function_single(cpu, ...) broadcast IPI to all other cpus?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Thu, 27 Jun 2024 10:12:07 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Marc Zyngier <maz@...nel.org>
Cc: richard clark <richard.xnu.clark@...il.com>, Mark Rutland
 <mark.rutland@....com>, will@...nel.org, linux-kernel@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org, "Russell King (Oracle)"
 <linux@...linux.org.uk>, Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: Will smp_call_function_single(cpu, ...) broadcast IPI to all
 other cpus?

On Thu, 27 Jun 2024 11:38:58 +0100
Marc Zyngier <maz@...nel.org> wrote:

> You may want to enable stack trace recording and find out for yourself
> where these ipi_raise() calls are coming from.

Try trace-cmd:

  # trace-cmd start -e ipi_raise -R 'stacktrace if reason=="Function call interrupts"'
  # taskset -c 0 insmod /kmods/ipi_test.ko
  # trace-cmd stop
  # trace-cmd show

-- Steve