From: Cyrill Gorcunov <gorcunov@openvz.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Lin Ming <ming.m.lin@intel.com>, Don Zickus <dzickus@redhat.com>,
Shaun Ruffell <sruffell@digium.com>,
Maciej Rutecki <maciej.rutecki@gmail.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Stephane Eranian <eranian@google.com>,
Robert Richter <robert.richter@amd.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip] perf, x86: fix unknown NMIs on a Pentium4 box
Date: Thu, 14 Apr 2011 21:46:00 +0400 [thread overview]
Message-ID: <4DA732D8.9040602@openvz.org> (raw)
In-Reply-To: <20110414174327.GA8863@elte.hu>
On 04/14/2011 09:43 PM, Ingo Molnar wrote:
...
>>
>> handled = x86_pmu.handle_irq(args->regs);
>> +
>> + /*
>> + * Note the unmasking of LVTPC entry must be
>> + * done *after* counter oveflow flag is cleared
>> + * otherwise it might lead to double NMIs generation.
>> + */
>> + apic_write(APIC_LVTPC, APIC_DM_NMI);
>> +
>> if (!handled)
>> return NOTIFY_DONE;
>>
>
> This breaks 'perf top' on Intel Nehalem and probably other CPUs. The NMI gets
> stuck fast on all CPUs:
>
> NMI: 16 6 3 3 3 3 3 3 3 3 3 3 3 3 4 5 Non-maskable interrupts
>
> Thanks,
>
> Ingo
Hmm. Thanks for info. Investigating...
--
Cyrill
next prev parent reply other threads:[~2011-04-14 17:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 14:48 [PATCH -tip] perf, x86: fix unknown NMIs on a Pentium4 box Cyrill Gorcunov
2011-04-14 15:03 ` Ingo Molnar
2011-04-14 15:06 ` Cyrill Gorcunov
2011-04-14 17:43 ` Ingo Molnar
2011-04-14 17:44 ` Ingo Molnar
2011-04-14 17:49 ` Cyrill Gorcunov
2011-04-14 18:12 ` Shaun Ruffell
2011-04-14 18:14 ` Cyrill Gorcunov
2011-04-14 18:19 ` Cyrill Gorcunov
2011-04-14 19:35 ` David Ahern
2011-04-14 17:46 ` Cyrill Gorcunov [this message]
2011-04-14 18:32 ` Don Zickus
2011-04-14 18:45 ` Ingo Molnar
2011-04-14 18:46 ` Ingo Molnar
2011-04-14 19:43 ` Cyrill Gorcunov
2011-04-14 19:57 ` Don Zickus
2011-04-14 20:05 ` Cyrill Gorcunov
2011-04-14 20:18 ` Cyrill Gorcunov
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=4DA732D8.9040602@openvz.org \
--to=gorcunov@openvz.org \
--cc=a.p.zijlstra@chello.nl \
--cc=dzickus@redhat.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
--cc=robert.richter@amd.com \
--cc=sruffell@digium.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