Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965169AbcKXNht convert rfc822-to-8bit (ORCPT ); Thu, 24 Nov 2016 08:37:49 -0500 Received: from mga09.intel.com ([134.134.136.24]:61292 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936137AbcKXNhr (ORCPT ); Thu, 24 Nov 2016 08:37:47 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,543,1473145200"; d="scan'208";a="790324886" From: "Liang, Kan" To: Jiri Olsa CC: "peterz@infradead.org" , "mingo@redhat.com" , "acme@kernel.org" , "linux-kernel@vger.kernel.org" , "alexander.shishkin@linux.intel.com" , "tglx@linutronix.de" , "namhyung@kernel.org" , "jolsa@kernel.org" , "Hunter, Adrian" , "wangnan0@huawei.com" , "mark.rutland@arm.com" , "andi@firstfloor.org" Subject: RE: [PATCH 06/14] perf tools: show NMI overhead Thread-Topic: [PATCH 06/14] perf tools: show NMI overhead Thread-Index: AQHSRbFV6SgYjdJvTUKEPgmaRMH4YqDmptyAgAFucLA= Date: Thu, 24 Nov 2016 13:37:04 +0000 Message-ID: <37D7C6CF3E00A74B8858931C1DB2F07750CA2BBA@SHSMSX103.ccr.corp.intel.com> References: <1479894292-16277-1-git-send-email-kan.liang@intel.com> <1479894292-16277-7-git-send-email-kan.liang@intel.com> <20161123225151.GC15978@krava> In-Reply-To: <20161123225151.GC15978@krava> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiOTg4NjFiOWItZGNmZi00YzkzLWFlM2YtMDc5M2M5NDE2YmI1IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6Ik5MV3pJcUZySEFoR1FwWVV3ek9JZmkxYjNHT1lFUDR1T2JiTFg0UUQ2RXc9In0= x-ctpclassification: CTP_IC x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1712 Lines: 60 > > On Wed, Nov 23, 2016 at 04:44:44AM -0500, kan.liang@intel.com wrote: > > From: Kan Liang > > > > Caculate the total NMI overhead on each CPU, and display them in perf > > report > > so the output looks like this: > > --- > # Elapsed time: 1720167944 ns > # Overhead: > # CPU 6 > # NMI#: 27 time: 111379 ns > # Multiplexing#: 0 time: 0 ns > # SB#: 57 time: 90045 ns > # > # Samples: 26 of event 'cycles:u' > # Event count (approx.): 1677531 > # > # Overhead Command Shared Object Symbol > # ........ ....... ................ ....................... > # > 24.20% ls ls [.] _init > 17.18% ls libc-2.24.so [.] __strcoll_l > 11.85% ls ld-2.24.so [.] _dl_relocate_object > --- > > > few things: > > - I wonder we want to put this overhead output separatelly from the > main perf out.. this scale bad with with bigger cpu counts > This output can only be shown when the user explicitly apply the --show-overhead option. I think the user should expect the big header. Or I can add --show-overhead-only option which only show the overhead information. It will like what we do for --header and --header-only Any suggestions? > - we might want to call it some other way, becayse we already > use 'overhead' for the event count % > "operating_cost"? "processing_cost"? "perf_cost"? "perf_overhead"? Suggestions? > - how about TUI output? ;-) I dont think it's necessary, however > currently 'perf report --show-overhead' does not show anything > ifTUI is default output, unless you use --stdio option I will try to add something in TUI mode. Thanks, Kan