From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933280AbbFJSop (ORCPT ); Wed, 10 Jun 2015 14:44:45 -0400 Received: from mail-ie0-f172.google.com ([209.85.223.172]:33125 "EHLO mail-ie0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754227AbbFJSog (ORCPT ); Wed, 10 Jun 2015 14:44:36 -0400 Message-ID: <55788592.8010701@gmail.com> Date: Wed, 10 Jun 2015 12:44:34 -0600 From: David Ahern User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Jiri Olsa , Arnaldo Carvalho de Melo CC: lkml , Adrian Hunter , Andi Kleen , Ingo Molnar , Namhyung Kim , Peter Zijlstra , Stephane Eranian Subject: Re: [PATCH 25/25] perf stat: Introduce --per-task option References: <1433959858-31858-1-git-send-email-jolsa@kernel.org> <1433959858-31858-26-git-send-email-jolsa@kernel.org> In-Reply-To: <1433959858-31858-26-git-send-email-jolsa@kernel.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 6/10/15 12:10 PM, Jiri Olsa wrote: > Currently all the -p option PID arguments tasks values > get aggregated and printed as single values. > > Adding --per-tasks option to print values per task. > > $ perf stat -e cycles,instructions --per-task -p 12451,16173 > ^C > Performance counter stats for process id '12451,16173': > > TASK-12451 77,784 cycles > TASK-16173 64,809 cycles > TASK-12451 14,432 instructions > TASK-16173 14,452 instructions > > 3.854957122 seconds time elapsed > > Also woks under interval mode: > > $ ./perf stat -e cycles,instructions --per-task -p 16431,16173 -I 1000 > # time task counts unit events > 1.000085816 TASK-16173 0 cycles > 1.000085816 TASK-16431 3,358,360,926 cycles > 1.000085816 TASK-16173 0 instructions > 1.000085816 TASK-16431 9,062,422,086 instructions > 2.000212262 TASK-16173 65,386 cycles > 2.000212262 TASK-16431 3,349,355,309 cycles > 2.000212262 TASK-16173 12,151 instructions > 2.000212262 TASK-16431 9,039,401,422 instructions > 3.000333402 TASK-16173 62,797 cycles > 3.000333402 TASK-16431 3,357,140,183 cycles > 3.000333402 TASK-16173 12,208 instructions > 3.000333402 TASK-16431 9,058,080,762 instructions > ^C 3.375949851 TASK-16173 0 cycles > 3.375949851 TASK-16431 1,264,764,804 cycles > 3.375949851 TASK-16173 0 instructions > 3.375949851 TASK-16431 3,414,532,317 instructions > Why not print $comm-$pid versus TASK-$pid?