linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: Andi Kleen <ak@linux.intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	"mingo@elte.hu" <mingo@elte.hu>,
	"Liang, Kan" <kan.liang@intel.com>, Jiri Olsa <jolsa@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: [PATCH 2/3] perf/x86/pebs: add workaround for broken OVFL status on HSW
Date: Thu, 10 Mar 2016 14:53:43 +0100	[thread overview]
Message-ID: <20160310135343.GL6375@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20160307121840.GF6375@twins.programming.kicks-ass.net>

On Mon, Mar 07, 2016 at 01:18:40PM +0100, Peter Zijlstra wrote:
> On Mon, Mar 07, 2016 at 11:24:13AM +0100, Peter Zijlstra wrote:
> 
> > I suspect Andi is having something along:
> > 
> >  lkml.kernel.org/r/1445458568-16956-1-git-send-email-andi@firstfloor.org
> > 
> > applied to his tree.
> 
> OK, I munged a bunch of patches together, please have a hard look at the
> end result found in:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git perf/core

So while running tip/master I just triggered the "irq loop stuck" warn
on my IVB, with status==1, and PMC0 didn't look weird at all.

I've not seen that for a fair while. But it does show it still happens
on not quite antique hardware.

  parent reply	other threads:[~2016-03-10 13:54 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03 19:50 [PATCH 0/3] perf/x86/pebs: various important fixes for PEBS Stephane Eranian
2016-03-03 19:50 ` [PATCH 1/3] perf/x86/intel: add definition for PT PMI bit Stephane Eranian
2016-03-08 13:16   ` [tip:perf/core] perf/x86/intel: Add " tip-bot for Stephane Eranian
2016-03-03 19:50 ` [PATCH 2/3] perf/x86/pebs: add workaround for broken OVFL status on HSW Stephane Eranian
2016-03-03 21:43   ` Andi Kleen
2016-03-03 23:40     ` Stephane Eranian
2016-03-07 10:24       ` Peter Zijlstra
2016-03-07 12:18         ` Peter Zijlstra
2016-03-07 18:27           ` Jiri Olsa
2016-03-07 20:25             ` Peter Zijlstra
2016-03-08 20:59               ` Stephane Eranian
2016-03-08 21:07                 ` Peter Zijlstra
2016-03-08 21:13                   ` Stephane Eranian
2016-03-09  5:34                     ` Stephane Eranian
2016-03-09  5:44                       ` Stephane Eranian
2016-03-09 17:40                         ` Stephane Eranian
2016-03-10 10:42                           ` Peter Zijlstra
2016-12-14 17:55                             ` Peter Zijlstra
2016-12-15  7:26                               ` Stephane Eranian
2016-12-15  7:52                                 ` Jiri Olsa
2016-12-15  8:04                                   ` Stephane Eranian
2016-12-15  8:42                                 ` Peter Zijlstra
2016-12-15 16:59                                   ` Stephane Eranian
2016-12-15 17:10                                     ` Peter Zijlstra
2016-12-16  8:38                                       ` Stephane Eranian
2016-12-16 17:48                                         ` Stephane Eranian
2016-03-10 13:53           ` Peter Zijlstra [this message]
2016-03-10 16:10             ` Stephane Eranian
2016-03-08 13:16   ` [tip:perf/core] perf/x86/pebs: Add workaround for broken OVFL status on HSW+ tip-bot for Stephane Eranian
2016-03-03 19:50 ` [PATCH 3/3] perf/x86/pebs: add proper PEBS constraints for Broadwell Stephane Eranian
2016-03-08 13:16   ` [tip:perf/core] perf/x86/pebs: Add " tip-bot for Stephane Eranian

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=20160310135343.GL6375@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@redhat.com \
    --cc=adrian.hunter@intel.com \
    --cc=ak@linux.intel.com \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=kan.liang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=namhyung@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;
as well as URLs for NNTP newsgroup(s).