linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Marc Zyngier <maz@kernel.org>
Cc: richard clark <richard.xnu.clark@gmail.com>,
	Mark Rutland <mark.rutland@arm.com>,
	will@kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	"Russell King (Oracle)" <linux@armlinux.org.uk>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Will smp_call_function_single(cpu, ...) broadcast IPI to all other cpus?
Date: Thu, 27 Jun 2024 10:12:07 -0400	[thread overview]
Message-ID: <20240627101207.0bbbead0@rorschach.local.home> (raw)
In-Reply-To: <86pls2isal.wl-maz@kernel.org>

On Thu, 27 Jun 2024 11:38:58 +0100
Marc Zyngier <maz@kernel.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


  reply	other threads:[~2024-06-27 14:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-27  9:26 Will smp_call_function_single(cpu, ...) broadcast IPI to all other cpus? richard clark
2024-06-27 10:38 ` Marc Zyngier
2024-06-27 14:12   ` Steven Rostedt [this message]
2024-06-28  1:57     ` richard clark
2024-06-28 10:21     ` richard clark
2024-06-28 12:41       ` Steven Rostedt
2024-06-29  5:41         ` richard clark
2024-06-28 13:13       ` Russell King (Oracle)
2024-06-29  5:38         ` 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=20240627101207.0bbbead0@rorschach.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=richard.xnu.clark@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).