Re: [PATCH 10/11] perf stat: Fix event grouping on forked task

[Arnaldo Carvalho de Melo]

Em Mon, Feb 13, 2012 at 04:27:42PM +0900, Namhyung Kim escreveu:
> When event group is enabled for forked task (i.e. no target task was
> specified) all events were disabled and marked ->enable_on_exec.
> However they are not counted at all since only group leader will be
> enabled on exec actually. So the result looked like below:
> 
>  $ perf stat --group sleep 1

This one is a bugfix and would be better if we have it isolated from
this patchset, not needing the cleanups, so that we can send it to
perf/urgent and stable@
 
>  Performance counter stats for 'sleep 1':
> 
>           0.530891 task-clock                #    0.001 CPUs utilized
>      <not counted> context-switches
>      <not counted> CPU-migrations
>      <not counted> page-faults
>      <not counted> cycles
>    <not supported> stalled-cycles-frontend
>    <not supported> stalled-cycles-backend
>      <not counted> instructions
>      <not counted> branches
>      <not counted> branch-misses
> 
>        1.001140177 seconds time elapsed
> 
> Fix it by disabling group leader only.
> 
> Signed-off-by: Namhyung Kim <namhyung.kim@xxxxxxx>
> ---
>  tools/perf/builtin-stat.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c
> index be2667236bea..2a592e52eaee 100644
> --- a/tools/perf/builtin-stat.c
> +++ b/tools/perf/builtin-stat.c
> @@ -297,7 +297,7 @@ static int create_perf_stat_counter(struct perf_evsel *evsel,
>  	if (maps.system_wide)
>  		return perf_evsel__open_per_cpu(evsel, evsel_list->cpus,
>  						group, group_fd);
> -	if (no_target_task(&maps)) {
> +	if (no_target_task(&maps) && (!group || evsel == first)) {
>  		attr->disabled = 1;
>  		attr->enable_on_exec = 1;
>  	}
> -- 
> 1.7.9
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/