Re: [PATCH 2/5] perf,tools: Support new sort type --socket

[Arnaldo Carvalho de Melo]

Em Fri, Sep 04, 2015 at 07:41:39PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Fri, Sep 04, 2015 at 10:45:43AM -0400, kan.liang@xxxxxxxxx escreveu:
> > From: Kan Liang <kan.liang@xxxxxxxxx>
> > 
> > This patch enable perf report to sort by processor socket
> > 
> > $ perf report --stdio --sort socket,comm,dso,symbol
> >  # To display the perf.data header info, please use
> >  --header/--header-only options.
> >  #
> >  #
> >  # Total Lost Samples: 0
> >  #
> >  # Samples: 686  of event 'cycles'
> >  # Event count (approx.): 349215462
> >  #
> >  # Overhead  SOCKET  Command    Shared Object     Symbol
> >  # ........  ......  .........  ................
> >  .................................
> 
> So this works in 'perf top' only for the first screen rendering, when it
> refreshes we lose the "SOCKET" header (why all caps?) and the colum
> stops being %03d and instead becomes %d, I am checking now.

Patch below fix this, but we stumble in another problem, when zooming it
is not eliding the SOCKET column, i.e. if we're zooming into a column,
it will have the same value for all entries, no use in showing it, save
some columns, will check that as well.

Will fold the fixes to the patches where the problems were introduced,
the feature is cool, one more zoom! :-)

Thanks,

- Arnaldo

diff --git a/tools/perf/util/hist.c b/tools/perf/util/hist.c
index bb633cd4730a..67b48616ab31 100644
--- a/tools/perf/util/hist.c
+++ b/tools/perf/util/hist.c
@@ -146,6 +146,7 @@ void hists__calc_col_len(struct hists *hists, struct hist_entry *h)
 		hists__set_unres_dso_col_len(hists, HISTC_MEM_DADDR_DSO);
 	}
 
+	hists__new_col_len(hists, HISTC_SOCKET, 6);
 	hists__new_col_len(hists, HISTC_MEM_LOCKED, 6);
 	hists__new_col_len(hists, HISTC_MEM_TLB, 22);
 	hists__new_col_len(hists, HISTC_MEM_SNOOP, 12);
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/