[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150907113630.GC5806@krava.brq.redhat.com>
Date: Mon, 7 Sep 2015 13:36:30 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: kan.liang@...el.com
Cc: acme@...nel.org, jolsa@...nel.org, a.p.zijlstra@...llo.nl,
luto@...nel.org, mingo@...hat.com, eranian@...gle.com,
ak@...ux.intel.com, mark.rutland@....com, adrian.hunter@...el.com,
namhyung@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V8 0/7] Freq/CPU%/CORE_BUSY% support
On Thu, Sep 03, 2015 at 08:30:56AM -0400, kan.liang@...el.com wrote:
> From: Kan Liang <kan.liang@...el.com>
>
> This patch set supports per-sample freq/CPU%/CORE_BUSY% print in perf
> report -D and --stdio.
> For printing these information, the perf.data file must have been obtained
> by group read and using special events cycles, ref-cycles, msr/tsc/,
> msr/aperf/ or msr/mperf/.
>
> - Freq (MHz): The frequency during the sample interval. Needs cycles
> ref-cycles event.
> - CPU%: CPU utilization during the sample interval. Needs ref-cycles and
> msr/tsc/ events.
> - CORE_BUSY%: actual percent performance (APERF/MPERF%) during the
> sample interval. Needs msr/aperf/ and msr/mperf/ events.
>
> Here is an example:
other than my latest 2 comments, I'm ok with the patchset
jirka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists