public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@openvz.org>
To: Don Zickus <dzickus@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>, "Huang, Ying" <ying.huang@intel.com>,
	"Maciej W. Rozycki" <macro@linux-mips.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip 2/2 resend] x86, traps: Drop nmi_reason_lock until it is really needed
Date: Wed, 02 Mar 2011 22:14:08 +0300	[thread overview]
Message-ID: <4D6E9700.50501@openvz.org> (raw)
In-Reply-To: <20110302184053.GW11359@redhat.com>

On 03/02/2011 09:40 PM, Don Zickus wrote:
> On Wed, Mar 02, 2011 at 07:13:42PM +0300, Cyrill Gorcunov wrote:
>> On 03/02/2011 07:03 PM, Ingo Molnar wrote:
>> ...
>>>
>>> Well, the lock serializes the read-out of the 'NMI reason' port, the handling of 
>>> whatever known reason and then the reassertion of the NMI (on 32-bit). 
>>>
>>> EDAC has a callback in pci_serr_error() - and this lock serializes that. So we 
>>> cannot just remove a lock like that, if there's any chance of parallel execution on 
>>> multiple CPUs.
>>>
>>> Thanks,
>>>
>>> 	Ingo
>>
>> OK, probably we need some UV person CC'ed (not sure whom) just to explain the
>> reason for such nmi-listening model. Meanwhile -- lets drop my patch.
> 
> It's for debugging reasons.  When their huge machine deadlocks, they
> wanted an easy mechanism to dump the cpu stacks.  That mechanism was an
> nmi button.  The problem was the button would only dump the first cpu.  By
> opening up the other cpus to accept external nmis, they could dump all the
> cpus.

  Yeah, thanks Don, just noted that (actually the former commit log
/78c06176466cbd1b3f0f67709d3023c40dbebcbd/ didn't mention that x86
masks only LVT1).

> 
> Now this spinlock doesn't affect them, because they registered an nmi
> handler to catch it and dump their stack (I modified the code to use
> DIE_NMIUNKNOWN instead of DIE_NMI to avoid conflict with the
> nmi_watchdog).  But I don't know what the affect is, if that spinlock is
> not there (I sent a private email to SGI inquiring, their guy wasn't
> around this week).

  Don, do you know -- was new nmi-watchdog system tested with UV machine
somewhere?

> 
> Personally I am indifferent to this patch.  I don't have any problems with
> the code the way it is now, but can understand what you mean having stuff
> lying around as 'dead code'.  I had thought Intel would have pushed more
> patches upstream to remove the BSP lock-in by now.
> 
> Cheers,
> Don
> 

-- 
    Cyrill

  reply	other threads:[~2011-03-02 19:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02 15:32 [PATCH -tip 2/2 resend] x86, traps: Drop nmi_reason_lock until it is really needed Cyrill Gorcunov
2011-03-02 15:46 ` Ingo Molnar
2011-03-02 15:55   ` Cyrill Gorcunov
2011-03-02 16:03     ` Ingo Molnar
2011-03-02 16:13       ` Cyrill Gorcunov
2011-03-02 18:40         ` Don Zickus
2011-03-02 19:14           ` Cyrill Gorcunov [this message]
2011-03-02 19:46             ` Don Zickus

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=4D6E9700.50501@openvz.org \
    --to=gorcunov@openvz.org \
    --cc=dzickus@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=mingo@elte.hu \
    --cc=ying.huang@intel.com \
    /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