Messages in this thread | | | Date | Fri, 25 Nov 2016 08:20:13 +0900 | From | Namhyung Kim <> | Subject | Re: [PATCH 06/14] perf tools: show NMI overhead |
| |
Hi,
On Thu, Nov 24, 2016 at 04:27:21PM +0100, Jiri Olsa wrote: > On Thu, Nov 24, 2016 at 01:37:04PM +0000, Liang, Kan wrote: > > > > > > > > > > On Wed, Nov 23, 2016 at 04:44:44AM -0500, kan.liang@intel.com wrote: > > > > From: Kan Liang <kan.liang@intel.com> > > > > > > > > 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 > > > --- > > how about we display the overhead information same way the main perf output: > > CPU NMI NMI time MTX MTX time SB SB time > ... ..... ........ ..... ........ ...... ........ > 6 27 111379 0 0 57 90045 > > > would be just matter of adding new sort objects
How would you connect those to hist entries then? It'd be possible if the sort key had 'cpu' only, no?
Thanks, Namhyung
| |