From: Thomas Gleixner <tglx@linutronix.de>
To: Wojciech Kudla <wk.kernel@gmail.com>, linux-kernel@vger.kernel.org
Cc: mingo@redhat.com, hpa@zytor.com, x86@kernel.org
Subject: Re: x86/smp: adding new trace points
Date: Wed, 13 May 2020 14:24:40 +0200 [thread overview]
Message-ID: <87y2pw2fav.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <b638ef03-04c2-94bf-f026-a01691888624@gmail.com>
Wojciech Kudla <wk.kernel@gmail.com> writes:
> I was trying to trace some IPIs (remote tlb shootdowns in this case) and noticed that:
>
> 1) irq_vectors:x86_platform_ipi_entry and irq_vectors:x86_platform_ipi_exit are not hit at all for my case. The backtrace on the receiving CPU:
>
> 0xffffffff81079535 flush_tlb_func_common.constprop.10+0x105/0x220 [kernel]
> 0xffffffff81079681 flush_tlb_func_remote+0x31/0x40 [kernel]
> 0xffffffff8111f76c flush_smp_call_function_queue+0x4c/0xf0 [kernel]
> 0xffffffff81120253 generic_smp_call_function_single_interrupt+0x13/0x30 [kernel]
> 0xffffffff81a030c6 smp_call_function_single_interrupt+0x36/0xd0 [kernel]
> 0xffffffff81a02679 call_function_single_interrupt+0xa9/0xb0 [kernel]
>
> I would expect that we would hit those trace point somewhere around
> call_function_single_interrupt()
Why would the SMP call function single interrupt go through the
PLATFORM_IPI_VECTOR? It goes as the name says through the
CALL_FUNCTION_SINGLE_VECTOR.
Thanks,
tglx
next prev parent reply other threads:[~2020-05-13 12:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4d54953b-f968-63f5-569f-9e09bc0f361c@gmail.com>
2020-05-12 11:39 ` x86/smp: adding new trace points Wojciech Kudla
2020-05-13 12:24 ` Thomas Gleixner [this message]
2020-05-13 14:42 ` Wojciech Kudla
2020-05-13 16:43 ` Thomas Gleixner
2020-05-13 18:42 ` Wojciech Kudla
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=87y2pw2fav.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=wk.kernel@gmail.com \
--cc=x86@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