linux-kernel - Re: [PATCH 31/52] perf stat record: Synthesize stat record data

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: <20151028130324.GA5216@krava.brq.redhat.com>
Date:	Wed, 28 Oct 2015 14:03:24 +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>,
	"Liang, Kan" <kan.liang@...el.com>
Subject: Re: [PATCH 31/52] perf stat record: Synthesize stat record data

On Tue, Oct 27, 2015 at 11:42:44AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Sun, Oct 25, 2015 at 03:51:47PM +0100, Jiri Olsa escreveu:
> > Synthesizing needed stat record data for report/script:
> >   - cpu/thread maps
> >   - stat config
> 
> After this it gets a bit better, but then I expected that to specify an
> event I would be able to use:
> 
> [root@zoo linux]# perf stat record -e cycles usleep 1
>   Error: unknown switch `e'
> 
>  Usage: perf record [<options>] [<command>]
>     or: perf record [<options>] -- <command> [<options>]
> 
>     -o, --output <file>   output file name
> 
> 
> But I need to do it as:
> 
> [root@zoo linux]# perf stat -e cycles record usleep 1
> 
>  Performance counter stats for 'usleep 1':
> 
>             948417      cycles                                                      
> 
>        0.000749965 seconds time elapsed
> 
> [root@zoo linux]# 
> 
> --------------------------------------------------
> 
> This is confusing...

yep, the thing is that we need to have all the options supported
by perf stat to work under perf stat record.

you basically let user use perf stat with 'record' that just says
'store the data I'm monitoring'

I'll try to find some way to move the options under perf stat record
without too many changes.. but not sure

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