All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Keith Owens <kaos@sgi.com>
Cc: linux-arch@vger.kernel.org
Subject: Re: [patch 2.6.17] Avoid broadcasting NMI IPIs
Date: Sat, 24 Jun 2006 10:36:53 +0200	[thread overview]
Message-ID: <200606241036.53597.ak@suse.de> (raw)
In-Reply-To: <23861.1151136920@ocs3.ocs.com.au>

On Saturday 24 June 2006 10:15, Keith Owens wrote:
> Andi Kleen (on Fri, 23 Jun 2006 14:32:56 +0200) wrote:
> >On Friday 23 June 2006 06:32, Keith Owens wrote:
> >> On some i386/x86_64 systems, sending an NMI IPI as a broadcast will
> >> reset the system.  This seems to be a BIOS bug which affects machines
> >> where one or more cpus are not under OS control.  It occurs on HT
> >> systems with a version of the OS that is not compiled without HT
> >> support.  It also occurs when a system is booted with max_cpus=n where
> >> 2 <= n < cpus known to the BIOS.  The fix is to always send NMI IPI as
> >> a mask instead of as a broadcast.
> >
> >Merged thanks.
> >
> >P.S.: Linux-arch isn't really the right list to cc x86 patches too.
> >I'm sure the other arch maintainers couldn't care less about such x86isms.
>
> These two patches were for both i386 and x86_64, not just for x86_64.

It's still not the right list for that. linux-arch is just to broadcast stuff
interesting to all architecture maintainers, not some kind of x86 list.

BTW  they didn't compile without fixes on x86-64-UP nor
i386-SMP. Please compile test patches better next time. 

-Andi

      reply	other threads:[~2006-06-24  8:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-23  4:32 [patch 2.6.17] Avoid broadcasting NMI IPIs Keith Owens
2006-06-23 12:32 ` Andi Kleen
2006-06-24  8:15   ` Keith Owens
2006-06-24  8:36     ` Andi Kleen [this message]

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=200606241036.53597.ak@suse.de \
    --to=ak@suse.de \
    --cc=kaos@sgi.com \
    --cc=linux-arch@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.