From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751273AbcAQQPi (ORCPT ); Sun, 17 Jan 2016 11:15:38 -0500 Received: from mx1.redhat.com ([209.132.183.28]:33838 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750884AbcAQQPh (ORCPT ); Sun, 17 Jan 2016 11:15:37 -0500 Date: Sun, 17 Jan 2016 17:15:33 +0100 From: Jiri Olsa To: Namhyung Kim Cc: Arnaldo Carvalho de Melo , Ingo Molnar , Peter Zijlstra , Jiri Olsa , LKML , David Ahern , Stephane Eranian , Andi Kleen , Wang Nan Subject: Re: [PATCH 01/17] perf hists: Basic support of hierarchical report view Message-ID: <20160117161533.GC17618@krava.redhat.com> References: <1452960197-5323-1-git-send-email-namhyung@kernel.org> <1452960197-5323-2-git-send-email-namhyung@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1452960197-5323-2-git-send-email-namhyung@kernel.org> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Jan 17, 2016 at 01:03:01AM +0900, Namhyung Kim wrote: SNIP > char *srcfile; > struct symbol *parent; > - struct rb_root sorted_chain; > struct branch_info *branch_info; > struct hists *hists; > struct mem_info *mem_info; > void *raw_data; > u32 raw_size; > void *trace_output; > + struct perf_hpp_fmt *fmt; > + struct hist_entry *parent_he; > + union { > + /* this is for hierarchical entry structure */ > + struct { > + struct rb_root hroot_in; > + struct rb_root hroot_out; > + }; /* non-leaf entries */ > + struct rb_root sorted_chain; /* leaf entry has callchains */ > + }; looks like cool feature! could we have the hist_entry storage little more generic? and maybe dynamically allocated? I'm doing the same thing for the c2c stuff, like having for each hist_entry its own 'struct hists' object, which records data related to parent hist_entry maybe we could strip the 'hists' object to some bare minimum which is needed for store/sort/stat and display entries in hists_browser ;-) I'm preparing RFC patchset in my perf/c2c branch, if you want to take a look however, as I said above, for my own sake it all boils down to have 'hists' object within hist_entry, so I can use it in the UI code easily FYI I also added support for hists object's own sort/output format lists.. which I'll curve out and send for review soon thanks, jirka