From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933679AbbFWOKn (ORCPT ); Tue, 23 Jun 2015 10:10:43 -0400 Received: from mga11.intel.com ([192.55.52.93]:30409 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933214AbbFWOKg (ORCPT ); Tue, 23 Jun 2015 10:10:36 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,665,1427785200"; d="scan'208";a="733013590" Message-ID: <55896847.8000105@intel.com> Date: Tue, 23 Jun 2015 17:08:07 +0300 From: Adrian Hunter Organization: Intel Finland Oy, Registered Address: PL 281, 00181 Helsinki, Business Identity Code: 0357606 - 4, Domiciled in Helsinki User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Arnaldo Carvalho de Melo , Jiri Olsa CC: Jiri Olsa , lkml , Andi Kleen , David Ahern , Ingo Molnar , Namhyung Kim , Peter Zijlstra , Stephane Eranian Subject: Re: [PATCHv4 00/27] perf stat: Introduce --per-thread option References: <1435012588-9007-1-git-send-email-jolsa@kernel.org> <20150622230600.GB8510@kernel.org> <20150623072200.GB749@krava.redhat.com> <20150623140501.GB3489@kernel.org> In-Reply-To: <20150623140501.GB3489@kernel.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 23/06/15 17:05, Arnaldo Carvalho de Melo wrote: > Em Tue, Jun 23, 2015 at 09:22:00AM +0200, Jiri Olsa escreveu: >> On Mon, Jun 22, 2015 at 08:06:00PM -0300, Arnaldo Carvalho de Melo wrote: >>> Em Tue, Jun 23, 2015 at 12:36:01AM +0200, Jiri Olsa escreveu: >>>> adding the possibility to display stat data per thread. > >>>> Allowing following commands and output: > >>>> $ perf stat -e cycles,instructions --per-thread -p 30190,30242 > >>> While testing Adrian's Intel PT patchkit I realised we have --per-thread >>> in 'record', wonder if using a long option with the exact same name but >>> different meanings for 'stat' and 'record' would cause confusion... > >> I think the name fits for both stat and record.. and both are doing different > > For record it is vague, for stat, it seems to fit. > > For record it really should be --mmap-per-thread, but then we start > getting what may seem overly long options, but then, its an oddball > 'record' option... It is not just the mmap, it is also the perf context. So it is central to the way perf works.