[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130723191413.GS6123@two.firstfloor.org>
Date: Tue, 23 Jul 2013 21:14:13 +0200
From: Andi Kleen <andi@...stfloor.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Andi Kleen <andi@...stfloor.org>, mingo@...nel.org,
linux-kernel@...r.kernel.org, Andi Kleen <ak@...ux.intel.com>,
eranian@...gle.com
Subject: Re: [PATCH] perf, x86: Enable PEBS mode automatically for
mem-{loads,stores} v3
On Tue, Jul 23, 2013 at 06:57:39PM +0200, Peter Zijlstra wrote:
> On Tue, Jul 23, 2013 at 06:13:34PM +0200, Andi Kleen wrote:
> > On Tue, Jul 23, 2013 at 10:38:34AM +0200, Peter Zijlstra wrote:
> > > On Thu, Jul 18, 2013 at 04:03:39PM -0700, Andi Kleen wrote:
> > > > From: Andi Kleen <ak@...ux.intel.com>
> > > >
> > > > [The patch to enable this in the user tools has been sent separately]
> > > >
> > > > With the earlier patches to automatically try cpu// and add
> > > > a precise sys attribute, we can now enable PEBS for the mem-loads,
> > > > mem-stores events everywhere.
> > > >
> > > > This allows to use
> > > >
> > > > perf record -e mem-loads ...
> > > >
> > > > instead of
> > > >
> > > > perf record -e cpu/mem-loads/p ...
> > > >
> > > > Always use precise=2 even though it is costly pre-Haswell
> > >
> > > This Changelog fails to give a reason _why_ we'd want to do this.
> >
> > The first is much nicer to type and understand? Just in the spirit of
> > making perf easier to use.
>
> And here I was thinking that maybe these events don't make sense without
> pebs or so. But no, rather than giving an actual useful reason you'd
> have me look things up myself. *sigh*
You can use them without PEBS, but they're much more useful with PEBS
(e.g. due to skid or if you want the address or data source, although
you can also use perf mem for the later)
I think PEBS on is a better default here.
BTW I should add i have some other events (for HSW TSX) that would
really like a PEBS default. That was the original motivation,
but then I realized it makes other things nicer too.
-Andi
--
ak@...ux.intel.com -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists