From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932163AbcF3Jkq (ORCPT ); Thu, 30 Jun 2016 05:40:46 -0400 Received: from merlin.infradead.org ([205.233.59.134]:56246 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932079AbcF3Jko (ORCPT ); Thu, 30 Jun 2016 05:40:44 -0400 Date: Thu, 30 Jun 2016 10:53:24 +0200 From: Peter Zijlstra To: Andi Kleen Cc: acme@kernel.org, jolsa@kernel.org, linux-kernel@vger.kernel.org, namhyung@kernel.org, Andi Kleen Subject: Re: [PATCH 5/9] perf, tools: Compute IPC and basic block cycles for annotate Message-ID: <20160630085324.GF30935@twins.programming.kicks-ass.net> References: <1437233094-12844-1-git-send-email-andi@firstfloor.org> <1437233094-12844-6-git-send-email-andi@firstfloor.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1437233094-12844-6-git-send-email-andi@firstfloor.org> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jul 18, 2015 at 08:24:50AM -0700, Andi Kleen wrote: > From: Andi Kleen > > Compute the IPC and the basic block cycles for the annotate display. > > IPC is computed by counting the instructions, and then dividing the > accounted cycles by that count. > > The actual IPC computation can only be done at annotate time, > because we need to parse the objdump output first to know > the number of instructions in the basic block. > > The cycles/IPC are also put into the perf function annotation > so that the display code can show them. > > Again basic block overlaps are not handled, with the longest winning, > but there are some heuristics to hide the IPC when the longest is not > the most common. I'm looking at basic block support, but this all seems to depend on the cycles stuff. Can we get the basic block stuff without that? I'm looking to plot the hottest path through a branchy function.