From: Peter Zijlstra <peterz@infradead.org>
To: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
mingo@kernel.org, alexander.shishkin@linux.intel.com,
hpa@zytor.com, bp@alien8.de, brgerst@gmail.com,
luto@amacapital.net, oleg@redhat.com, akpm@linux-foundation.org,
tglx@linutronix.de, dvlasenk@redhat.com
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/urgent] perf/x86/intel: Fix PMI handling for Intel PT
Date: Wed, 24 Jun 2015 14:21:21 +0200 [thread overview]
Message-ID: <20150624122121.GL3644@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <tip-1b7b938f181742f899a2f31c280f79dabef6ddb6@git.kernel.org>
On Fri, Jun 19, 2015 at 10:58:36AM -0700, tip-bot for Alexander Shishkin wrote:
> Commit-ID: 1b7b938f181742f899a2f31c280f79dabef6ddb6
> Gitweb: http://git.kernel.org/tip/1b7b938f181742f899a2f31c280f79dabef6ddb6
> Author: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> AuthorDate: Tue, 9 Jun 2015 13:03:26 +0300
> Committer: Ingo Molnar <mingo@kernel.org>
> CommitDate: Fri, 19 Jun 2015 09:38:47 +0200
>
> perf/x86/intel: Fix PMI handling for Intel PT
And the price goes to....
The result is very reproducible and the bisection is good, as reverting
this one commit makes it go away.
I've just finished, have not actually looked at the code yet, I need to
eat first.
---
root@ivb-ep:/usr/src/linux-2.6# perf record -a -e cycles:pp -- make
O=defconfig-build/ clean; make O=defconfig-build/ defconfig; make
O=defconfig-build/ -j80 -s
results in fail:
[ 45.618402] Uhhuh. NMI received for unknown reason 21 on CPU 0.
[ 45.625020] Do you have a strange power saving mode enabled?
[ 45.631336] Dazed and confused, but trying to continue
[ 49.736011] Uhhuh. NMI received for unknown reason 31 on CPU 3.
[ 49.742627] Do you have a strange power saving mode enabled?
[ 49.748954] Dazed and confused, but trying to continue
[ 50.317877] Uhhuh. NMI received for unknown reason 31 on CPU 26.
[ 50.324591] Do you have a strange power saving mode enabled?
[ 50.330917] Dazed and confused, but trying to continue
[ 50.950088] Uhhuh. NMI received for unknown reason 31 on CPU 27.
[ 50.956804] Do you have a strange power saving mode enabled?
[ 50.963129] Dazed and confused, but trying to continue
next prev parent reply other threads:[~2015-06-24 12:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 12:13 [PATCH 0/2] perf/x86/intel: Fixes for PT and BTS Alexander Shishkin
2015-06-11 12:13 ` [PATCH 1/2] perf/x86/intel/bts: Fix DS area sharing with x86_pmu events Alexander Shishkin
2015-06-19 17:58 ` [tip:perf/urgent] " tip-bot for Alexander Shishkin
2015-06-11 12:13 ` [PATCH 2/2] perf/x86/intel: Fix PMI handling for Intel PT Alexander Shishkin
2015-06-11 14:00 ` Peter Zijlstra
2015-06-12 9:08 ` Alexander Shishkin
2015-06-12 13:09 ` Peter Zijlstra
2015-06-19 17:58 ` [tip:perf/urgent] " tip-bot for Alexander Shishkin
2015-06-24 12:21 ` Peter Zijlstra [this message]
2015-06-24 13:16 ` Peter Zijlstra
2015-06-24 14:47 ` Peter Zijlstra
2015-07-01 6:57 ` [tip:perf/urgent] perf/x86: Fix 'active_events' imbalance tip-bot for Peter Zijlstra
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=20150624122121.GL3644@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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