linux-kernel - Re: [GIT PULL 00/43] perf/core new feature: 'perf stat record/report'

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] [day] [month] [year] [list]

Message-ID: <20151218101105.GA670@krava.brq.redhat.com>
Date:	Fri, 18 Dec 2015 11:11:05 +0100
From:	Jiri Olsa <jolsa@...hat.com>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	Arnaldo Carvalho de Melo <acme@...nel.org>,
	linux-kernel@...r.kernel.org,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	David Ahern <dsahern@...il.com>, Jiri Olsa <jolsa@...nel.org>,
	Kan Liang <kan.liang@...el.com>,
	Namhyung Kim <namhyung@...nel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Wang Nan <wangnan0@...wei.com>
Subject: Re: [GIT PULL 00/43] perf/core new feature: 'perf stat record/report'

On Fri, Dec 18, 2015 at 09:55:38AM +0100, Ingo Molnar wrote:

SNIP

> 
> Right now if I do 'perf report' on such a perf.data then I'll get a "no samples" 
> TUI message, which is technically correct but somewhat misleading.
> 
> It's no big deal - and maybe you guys can think of a better solution than 
> displaying an error message: maybe 'perf report' should automatically switch to 
> 'perf stat report'?
> 
> It would be a bit shorter to type as well and would continue to strengthen the 
> very nice level of integration that the various subcommands already have today.
> 
> But maybe it would be confusing - don't know.

let's see ;-) I'll try to send out rfc soon

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