From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Don Zickus <dzickus@redhat.com>
Cc: x86@kernel.org, Peter Zijlstra <peterz@infradead.org>,
Robert Richter <robert.richter@amd.com>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] perf, nmi: Move LVT un-masking into irq handlers
Date: Wed, 20 Apr 2011 19:03:02 +0400 [thread overview]
Message-ID: <4DAEF5A6.4040405@gmail.com> (raw)
In-Reply-To: <20110420145754.GT20887@redhat.com>
On 04/20/2011 06:57 PM, Don Zickus wrote:
> On Wed, Apr 20, 2011 at 06:37:10PM +0400, Cyrill Gorcunov wrote:
>> Don, sorry for delay, I somehow missed this patch at first place :/ And probably
>> the patch below could help with "stess" problem?
>
> The patch I am using for the 'stress' problem is different than what I
> posted because I wanted to keep it simple for 2.6.39. But yeah I already
> moved the unmasking to the enable_pmus_all(0) line.
ok
>
> The thing is that cuts down on some of these in-flight NMIs but not all of
> them. I came up with some logic that catches all the in-flight NMIs on
> Nehalem and AMDs but my core2quad still fails. I'll try to post that
> today while requesting help.
ok
>
> Still not sure you need the double APIC writes (as your patch) shows. I
> haven't seen a case in my testing where a single APIC write fails.
yup, we can drop it, thanks!
>
> Cheers,
> Don
--
Cyrill
next prev parent reply other threads:[~2011-04-20 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 16:56 [PATCH] perf, nmi: Move LVT un-masking into irq handlers Don Zickus
2011-04-20 14:37 ` Cyrill Gorcunov
2011-04-20 14:57 ` Don Zickus
2011-04-20 15:03 ` Cyrill Gorcunov [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-27 10:32 Don Zickus
2011-04-27 17:26 ` 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=4DAEF5A6.4040405@gmail.com \
--to=gorcunov@gmail.com \
--cc=dzickus@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=robert.richter@amd.com \
--cc=x86@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