All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Vince Weaver <vincent.weaver@maine.edu>,
	LKML <linux-kernel@vger.kernel.org>,
	Stephane Eranian <eranian@google.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ingo Molnar <mingo@redhat.com>, Paul Mackerras <paulus@samba.org>
Subject: Re: perf: odd event scheduling issue
Date: Wed, 20 May 2015 09:11:38 +0200	[thread overview]
Message-ID: <20150520071138.GD26714@krava.redhat.com> (raw)
In-Reply-To: <20150520070057.GK3644@twins.programming.kicks-ass.net>

On Wed, May 20, 2015 at 09:00:57AM +0200, Peter Zijlstra wrote:
> On Tue, May 19, 2015 at 11:07:09PM -0400, Vince Weaver wrote:
> > Hello
> > 
> > so I'm running 4.1-rc4 on my Haswell machine and a lot of my perf_event 
> > testsuite is failing.  There seems to be weird event scheduling issues.
> > 
> > I can reproduce it with plain perf; simple event groups that should work 
> > fine can't be scheduled.
> > 
> > vince@haswell:~$ perf stat -e \{cycles,instructions\} sleep 1
> > 
> 
> Hmm indeed, my ivb-ep does the same thing. Lemme go poke at that.

snb is ok

jirka

  reply	other threads:[~2015-05-20  7:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20  3:07 perf: odd event scheduling issue Vince Weaver
2015-05-20  7:00 ` Peter Zijlstra
2015-05-20  7:11   ` Jiri Olsa [this message]
2015-05-20  9:28   ` Peter Zijlstra
2015-05-20 13:52     ` Peter Zijlstra
2015-05-20 15:25       ` Peter Zijlstra
2015-05-20 16:08         ` Peter Zijlstra
2015-05-20 16:28           ` Peter Zijlstra
2015-05-20 23:10             ` Andi Kleen
2015-05-21 12:04               ` Stephane Eranian
2015-05-20 16:25       ` Jiri Olsa
2015-05-21 12:05         ` 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=20150520071138.GD26714@krava.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=vincent.weaver@maine.edu \
    /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.