From: Andi Kleen <ak@suse.de>
To: "Brendan Trotter" <btrotter@gmail.com>
Cc: "Keith Owens" <kaos@sgi.com>, "Ashok Raj" <ashok.raj@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: NMI problems with Dell SMP Xeons
Date: Wed, 7 Jun 2006 17:23:05 +0200 [thread overview]
Message-ID: <200606071723.05921.ak@suse.de> (raw)
In-Reply-To: <b1ebdcad0606070818l3024b264k89f6cd37ccb0b6f7@mail.gmail.com>
> The "send_IPI_mask_sequence()" function also seems like a perfectly
> valid option (except for the comments, which are easy enough to
> change). IMHO it's just not as pretty, especially if it's to be used
> for all broadcast IPIs (rather than just for broadcast NMIs) - I'd be
> tempted to do an "#ifdef BORKED_DELL" around it in that case. :-)
It's not only that Dell that has trouble with broadcasts. On newer platforms
which support CPU hotplug there are races at the hardware level with
broadcasting. That is why we're moving away from it.
Not sure why this particular case got missed. Ashok might want to comment -
he did the hotplug work.
-Andi
next prev parent reply other threads:[~2006-06-07 15:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 9:08 NMI problems with Dell SMP Xeons Keith Owens
2006-05-22 23:56 ` Andi Kleen
2006-05-23 1:26 ` Keith Owens
2006-05-23 1:55 ` Andi Kleen
2006-05-23 2:02 ` Keith Owens
2006-05-23 2:21 ` Keith Owens
2006-05-23 5:03 ` Keith Owens
2006-06-07 4:49 ` Keith Owens
2006-06-07 7:20 ` Andi Kleen
2006-06-07 7:43 ` Keith Owens
2006-06-07 8:01 ` Andi Kleen
2006-06-07 11:47 ` Keith Owens
2006-06-07 12:13 ` Andi Kleen
2006-06-07 15:18 ` Brendan Trotter
2006-06-07 15:23 ` Andi Kleen [this message]
2006-06-07 18:47 ` Rajesh Shah
2006-06-08 0:41 ` Rajesh Shah
2006-06-08 0:46 ` Rajesh Shah
2006-06-08 5:11 ` Keith Owens
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=200606071723.05921.ak@suse.de \
--to=ak@suse.de \
--cc=ashok.raj@intel.com \
--cc=btrotter@gmail.com \
--cc=kaos@sgi.com \
--cc=linux-kernel@vger.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