Messages in this thread | | | From | "Liang, Kan" <> | Subject | RE: [PATCH V7 6/8] perf,tools: Dump per-sample freq/CPU%/CORE_BUSY% in report -D | Date | Mon, 31 Aug 2015 19:10:44 +0000 |
| |
> On Fri, Aug 28, 2015 at 05:48:07AM -0400, Kan Liang wrote: > > From: Kan Liang <kan.liang@intel.com> > > > > The group read results from cycles/ref-cycles/TSC/ASTATE/MSTATE > event > > can be used to calculate the frequency, CPU Utilization and percent > > performance during each sampling period. > > This patch shows them in report -D. > > > > Here is an example: > > > > $ perf record -e > > '{cycles,ref-cycles,msr/tsc/,msr/mperf/,msr/aperf/}:S' ~/tchain_edit > > so this perf cord set of events is set when you want to get the freq > data/ratios.. I think we should not force user to specify this on command > line and provide short option for that like > > $ perf record --freq ~/tchain_edit > > we already do this in perf stat for transactions.. you can also check the > existence of particular events and warn user appropriatelly if any is missing > Yes, we can do that, but should be in separate patch.
Thanks, Kan
| |