From: Peter Zijlstra <peterz@infradead.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Nikolay Borisov <kernel@kyup.com>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
andi@firstfloor.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Strange behavior of perf top with PEBS
Date: Mon, 8 Aug 2016 15:03:43 +0200 [thread overview]
Message-ID: <20160808130343.GF6879@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20160805102320.GB12528@krava>
On Fri, Aug 05, 2016 at 12:23:20PM +0200, Jiri Olsa wrote:
> On Fri, Aug 05, 2016 at 12:30:32PM +0300, Nikolay Borisov wrote:
> >
> >
> > On 08/04/2016 06:29 PM, Jiri Olsa wrote:
> > > On Tue, Jul 26, 2016 at 02:30:46PM +0300, Nikolay Borisov wrote:
> > [SNIP]
> > >
> > > sorry for late response..
> > >
> > > I checked on f22 kernel and it's missing the core2 PEBs fix:
> > > 1424a09a9e18 perf/x86: fix PEBS issues on Intel Atom/Core2
> > >
> > > which was introduced in 4.5.. you should upgrade or include
> > > this patch
> > >
> >
> > Thanks for the reply. Isn't this supposed to be tagged as stable since
> > it essentially breaks the default invocation of perf top?
>
> yep, it seems like good one to have in stable, Peter?
Greg, could you pick:
1424a09a9e18 ("perf/x86: fix PEBS issues on Intel Atom/Core2")
Into 4.4-stable ?
next prev parent reply other threads:[~2016-08-08 13:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 13:28 Strange behavior of perf top with PEBS Nikolay Borisov
2016-07-20 14:34 ` Jiri Olsa
2016-07-20 14:36 ` Nikolay Borisov
2016-07-20 14:38 ` Jiri Olsa
2016-07-26 11:30 ` Nikolay Borisov
2016-08-04 15:29 ` Jiri Olsa
2016-08-05 9:30 ` Nikolay Borisov
2016-08-05 10:23 ` Jiri Olsa
2016-08-08 13:03 ` Peter Zijlstra [this message]
2016-08-08 13:19 ` Greg Kroah-Hartman
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=20160808130343.GF6879@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=andi@firstfloor.org \
--cc=gregkh@linuxfoundation.org \
--cc=jolsa@redhat.com \
--cc=kernel@kyup.com \
--cc=linux-kernel@vger.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 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.