From: Keith Owens <kaos@sgi.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-arch@vger.kernel.org
Subject: Re: [patch 2.6.17] Standardize i386/x86_64 handling of NMI_VECTOR
Date: Thu, 22 Jun 2006 22:09:42 +1000 [thread overview]
Message-ID: <29012.1150978182@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Thu, 22 Jun 2006 13:59:46 +0200." <200606221359.46092.ak@suse.de>
Andi Kleen (on Thu, 22 Jun 2006 13:59:46 +0200) wrote:
>On Thursday 22 June 2006 13:46, Keith Owens wrote:
>> Andi Kleen (on Thu, 22 Jun 2006 12:48:21 +0200) wrote:
>> >On Thursday 22 June 2006 11:01, Keith Owens wrote:
>> >> x86_64 and i386 behave inconsistently when sending an IPI on vector 2
>> >> (NMI_VECTOR). Make both behave the same, so IPI 2 is sent as NMI.
>> >>
>> >> The crash code was abusing send_IPI_allbutself() by passing a code
>> >> instead of a vector, it only worked because crash knew about the
>> >> internal code of send_IPI_allbutself(). Change crash to use NMI_VECTOR
>> >> instead, and remove the comment about how crash was abusing the function.
>> >
>> >Does that fix anything?
>>
>> This patch is a pre-requisite for fixing the problem where sending an
>> IPI as NMI would reboot some Dell Xeon systems. I cannot fix that
>> problem while crash continus to abuse send_IPI_allbutself().
>
>I merged it with the updated description. Thanks.
Merged how much and into which tree? Most of the change is i386, with
a one line change to x86_64. I have to ensure that the i386 bits get
into the main tree.
prev parent reply other threads:[~2006-06-22 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 9:01 [patch 2.6.17] Standardize i386/x86_64 handling of NMI_VECTOR Keith Owens
2006-06-22 10:48 ` Andi Kleen
2006-06-22 11:46 ` Keith Owens
2006-06-22 11:59 ` Andi Kleen
2006-06-22 12:09 ` Keith Owens [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=29012.1150978182@ocs3.ocs.com.au \
--to=kaos@sgi.com \
--cc=ak@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox