Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751414AbaBGEEa (ORCPT ); Thu, 6 Feb 2014 23:04:30 -0500 Received: from alerce.vps.bitfolk.com ([85.119.82.134]:47225 "EHLO alerce.vps.bitfolk.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750818AbaBGEE3 (ORCPT ); Thu, 6 Feb 2014 23:04:29 -0500 X-Greylist: delayed 1958 seconds by postgrey-1.27 at vger.kernel.org; Thu, 06 Feb 2014 23:04:29 EST Date: Fri, 7 Feb 2014 03:31:10 +0000 From: Rodrigo Campos To: Namhyung Kim Cc: Arnaldo Carvalho de Melo , Peter Zijlstra , Ingo Molnar , Paul Mackerras , Namhyung Kim , LKML , Arun Sharma , Frederic Weisbecker , Andi Kleen , David Ahern Subject: Re: [PATCHSET 00/21] perf tools: Add support to accumulate hist periods (v8) Message-ID: <20140207033110.GA17630@sdfg.com.ar> References: <1391736923-30765-1-git-send-email-namhyung@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1391736923-30765-1-git-send-email-namhyung@kernel.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 07, 2014 at 10:35:02AM +0900, Namhyung Kim wrote: > > Currently the perf enables both of --call-graph and --children when it > finds callchains in the samples. While this is useful for TUI or GTK, > I'm not sure for stdio as it'd consume so much lines. > > It does not handle all kind of cases like event groups and annotations > yet, but I really want to release it and get reviews. > > You can also get this series on 'perf/cumulate-v8' branch in my tree at: > > git://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git I've modified a little your example to link against two libraries dynamically and see different cases of how is self vs children attributed when running with "--sort dso" and it seems great. I've tried simple examples just as: calling a lib1 function that calls lib2 function which uses lot of CPU, calling lib1 function that uses lot of CPU and also calls lib2 func that uses lot of CPU. And things like that. Probably using one lib was enough (I first played with only one) as it's a different symbol from the main, but just in case some weird bug (was really easy) I tested with two :-) I might be able to test with more real world scenarios on Saturday, although I'm sick now and I'm not sure how I will feel :S Thanks a lot! Rodrigo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/