linux-kernel - Re: [PATCH 2/3] perf stat: Don't require a workload when using system wide or CPU options

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]

Date:	Tue, 08 Oct 2013 07:42:49 -0600
From:	David Ahern <dsahern@...il.com>
To:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
CC:	Namhyung Kim <namhyung@...nel.org>, linux-kernel@...r.kernel.org,
	Ingo Molnar <mingo@...nel.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Jiri Olsa <jolsa@...hat.com>,
	Namhyung Kim <namhyung.kim@....com>,
	Stephane Eranian <eranian@...gle.com>
Subject: Re: [PATCH 2/3] perf stat: Don't require a workload when using system
 wide or CPU options

On 10/8/13 7:33 AM, Arnaldo Carvalho de Melo wrote:
> [acme@zoo linux]$ perf stat non-existent-proggie
> non-existent-proggie: No such file or directory

ok. so this is a different error. need to detect the workload does not 
exist.

> Why should we report all those counters for something that wasn't found
> in PATH?
>
> We either report just the first line, with the errno, or that and the
> last, with how long it took to try to execute it, but that probably
> shouldn't be printed, as it is supposed to be how long the workload ran,
> right?

Right. need to feed/detect the exec failure back to the parent.

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