From: Jiri Olsa <jolsa@redhat.com>
To: kan.liang@intel.com
Cc: acme@kernel.org, jolsa@kernel.org, a.p.zijlstra@chello.nl,
luto@kernel.org, mingo@redhat.com, eranian@google.com,
ak@linux.intel.com, mark.rutland@arm.com,
adrian.hunter@intel.com, namhyung@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V8 0/7] Freq/CPU%/CORE_BUSY% support
Date: Mon, 7 Sep 2015 13:36:30 +0200 [thread overview]
Message-ID: <20150907113630.GC5806@krava.brq.redhat.com> (raw)
In-Reply-To: <1441283463-51050-1-git-send-email-kan.liang@intel.com>
On Thu, Sep 03, 2015 at 08:30:56AM -0400, kan.liang@intel.com wrote:
> From: Kan Liang <kan.liang@intel.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
prev parent reply other threads:[~2015-09-07 11:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 12:30 kan.liang
2015-09-03 12:30 ` [PATCH V8 1/7] perf,tools: introduce generic FEAT for CPU attributes kan.liang
2015-09-03 12:30 ` [PATCH V8 2/7] perf,tools: read msr pmu type from header kan.liang
2015-09-03 12:30 ` [PATCH V8 3/7] perf, record: introduce --freq-perf option kan.liang
2015-09-07 10:57 ` Jiri Olsa
2015-09-08 15:21 ` Liang, Kan
2015-09-03 12:31 ` [PATCH V8 4/7] perf,tools: fix dump_sample crash when evsel is NULL kan.liang
2015-09-08 14:38 ` [tip:perf/core] perf session: Don't call dump_sample() " tip-bot for Kan Liang
2015-09-03 12:31 ` [PATCH V8 5/7] perf,tools: Dump per-sample freq/CPU%/CORE_BUSY% in report -D kan.liang
2015-09-03 12:31 ` [PATCH V8 6/7] perf,tools: caculate and save freq/CPU%/CORE_BUSY% in he_stat kan.liang
2015-09-03 12:31 ` [PATCH V8 7/7] perf,tools: Show freq/CPU%/CORE_BUSY% in perf report --stdio kan.liang
2015-09-07 11:17 ` Jiri Olsa
2015-09-07 11:36 ` Jiri Olsa [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150907113630.GC5806@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®