From: Mike Galbraith <efault@gmx.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>
Subject: x86_64: can boxen lose IPIs during IPI storm?
Date: Wed, 22 Aug 2012 14:59:16 +0200 [thread overview]
Message-ID: <1345640356.26849.59.camel@marge.simpson.net> (raw)
Greetings,
Not so hypothetical situation: CPUs are having a major SCSI induced IPI
fest, printk via serial port is happening while the storm is raging.
Can it happen that while IRQs are disabled, multiple IPIs arrive, thus
losing one or more? Seems like that possibility _has_ to be excluded by
hardware for SMP to actually work (and it generally does;) but...
I ask because of a dump I saw, where CPU3 waits for CPU1 forever after
having IPId all CPUs, with all except CPU1 having responded. CPU1,
seemingly unaware of any such IPI, was then used to trigger that very
dump, ie was not busted/stuck, which looked rather like a lost IPI.
-Mike
reply other threads:[~2012-08-22 12:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1345640356.26849.59.camel@marge.simpson.net \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®