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

[Arnaldo Carvalho de Melo <acme@ghostprotocols.net>]

Em Tue, Oct 08, 2013 at 07:25:39AM -0600, David Ahern escreveu:
> On 10/8/13 6:39 AM, Arnaldo Carvalho de Melo wrote:
> >While trying it noticed this, that should also be fixed
> >eventually:

> >[root@zoo ~]# perf stat -c C 0
> >C: No such file or directory
 
> you are missing '-' before the C:  perf stat -C 0. The -C = cpus. -c
> for stat is scale.

Nah, I mean:

[acme@zoo linux]$ perf stat non-existent-proggie
non-existent-proggie: No such file or directory

 Performance counter stats for 'non-existent-proggie':

     <not counted> task-clock              
     <not counted> context-switches        
     <not counted> cpu-migrations          
     <not counted> page-faults             
     <not counted> cycles                  
     <not counted> stalled-cycles-frontend 
   <not supported> stalled-cycles-backend  
     <not counted> instructions            
     <not counted> branches                
     <not counted> branch-misses           

       0.001823577 seconds time elapsed

[acme@zoo linux]$

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?

- Arnaldo