linux-kernel - Re: [PATCH] perf, x86: Enable PEBS mode automatically for mem-{loads,stores} v3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130723161334.GQ6123@two.firstfloor.org>
Date:	Tue, 23 Jul 2013 18:13:34 +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 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.

-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/