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
| ||
|
Date: Sat, 26 Mar 2016 17:06:38 +0100 From: Jiri Olsa <jolsa@...hat.com> To: Arnaldo Carvalho de Melo <acme@...nel.org> Cc: Jiri Olsa <jolsa@...nel.org>, lkml <linux-kernel@...r.kernel.org>, David Ahern <dsahern@...il.com>, Ingo Molnar <mingo@...nel.org>, Namhyung Kim <namhyung@...nel.org>, Peter Zijlstra <a.p.zijlstra@...llo.nl>, Stephane Eranian <eranian@...gle.com>, Andi Kleen <ak@...ux.intel.com> Subject: Re: [PATCH 1/6] perf mem: Add --ldlat option On Thu, Mar 24, 2016 at 12:57:58PM -0300, Arnaldo Carvalho de Melo wrote: > Em Thu, Mar 24, 2016 at 01:52:15PM +0100, Jiri Olsa escreveu: > > Adding --ldlat option to specify desired latency > > for loads event. > > > > Specify 50 as loads event latency: > > > > $ perf mem record -e ldlat-loads -v --ldlat 50 true > > calling: record -W -d -e cpu/mem-loads,ldlat=50/P true > > We have all this infrastructure to set per-event settings, on the > command line, and here we end up adding a separate command line option > to do that? Why not something like: > > perf mem record -e ldlat-loads/lat=50/ true will check ;-) thanks, jirka
Powered by blists - more mailing lists