All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Don Zickus <dzickus@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>, George Spelvin <linux@horizon.com>,
	Meelis Roos <mroos@linux.ee>, Lin Ming <ming.m.lin@intel.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	lkml <linux-kernel@vger.kernel.org>,
	Jason Wessel <jason.wessel@windriver.com>
Subject: Re: [PATCH] perf, x86: P4 PMU -- Fix unflagged overflows test
Date: Mon, 07 Feb 2011 20:22:21 +0300	[thread overview]
Message-ID: <4D502A4D.1040301@gmail.com> (raw)
In-Reply-To: <4D4EF4BC.6040206@gmail.com>

On 02/06/2011 10:21 PM, Cyrill Gorcunov wrote:
> On 02/04/2011 07:59 PM, Don Zickus wrote:
>> On Fri, Feb 04, 2011 at 03:17:28PM +0300, Cyrill Gorcunov wrote:
>>> Please apply it, sorry for non-inlined patch (have a web access only at moment).
>>>
>>> Note that I've tested the patch on non-HT machine so if someone have HT'ed one
>>> -- it would be great to test the patch there.
>>
>> Hmm. For some reason, when I enable the kgdb testsuite, the box fails to
>> boot with hardlockup issues.  It seems like the code is swallowing the
>> NMIs? I basically applied this patch on top of 2.6.38-rc3 and ran it on my
>> Xeon box (p4 w/HT).
>>
>> Cheers,
>> Don
> 
>   Don, I hope to get access to p4 machine tomorrow and investigate this issue
> (didn't manage to read kgdb code this weekend). Sorry for delay.
> 

  Just for info -- I've tested the patch on p4 machine with kgdb bootup tests
and results are somehow strange. If I disable nmi-watchdog the tests passes
fine and i'm able to run perf top (or anything related). Same time if I leave
nmi-watchdog enabled by default the borrowed event reported, kgdb tests passes
but nmi-watchdog never fires (ie I see nmi irq counter remains zero). So I've added
debug prints and found that counter reaches positive values and didn't issues
nmi at all. All in one -- i'm still investigating this issue unfortunatelly
the kernel build procedure sometime takes hours on this machine (even with
ccache enabled) so it goes a way slower then I expected :(
-- 
    Cyrill

  reply	other threads:[~2011-02-07 17:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04 12:17 [PATCH] perf, x86: P4 PMU -- Fix unflagged overflows test Cyrill Gorcunov
2011-02-04 16:59 ` Don Zickus
2011-02-04 17:32   ` Cyrill Gorcunov
2011-02-06 19:21   ` Cyrill Gorcunov
2011-02-07 17:22     ` Cyrill Gorcunov [this message]
2011-02-08 14:26       ` George Spelvin
2011-02-08 14:38         ` Cyrill Gorcunov
2011-02-05  2:28 ` George Spelvin
2011-02-05  8:40   ` Cyrill Gorcunov
2011-02-05  9:15     ` George Spelvin
2011-02-05  9:22       ` 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=4D502A4D.1040301@gmail.com \
    --to=gorcunov@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=dzickus@redhat.com \
    --cc=jason.wessel@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@horizon.com \
    --cc=ming.m.lin@intel.com \
    --cc=mingo@elte.hu \
    --cc=mroos@linux.ee \
    /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.