From: Stephane Eranian <eranian@google.com>
To: Andi Kleen <ak@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"mingo@elte.hu" <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung.kim@lge.com>
Subject: Re: [PATCH 0/2] perf stat: add per-core count aggregation
Date: Tue, 12 Feb 2013 18:33:42 +0100 [thread overview]
Message-ID: <CABPqkBQBnN8y7WWWye1e0goJ6On1SYOKWsUG9=R76+d7ScWLDg@mail.gmail.com> (raw)
In-Reply-To: <20130212172951.GD30387@tassilo.jf.intel.com>
On Tue, Feb 12, 2013 at 6:29 PM, Andi Kleen <ak@linux.intel.com> wrote:
>>
>> > The idea itself is useful.
>> >
>> Yes, it is.
>
> BTW it would be even more useful if it could print some of the
> statistics turbostat does (in particular frequency and C0 residency)
> Often you only care about cycles not idle, and the frequency
> tells you how fast the cycles happen.
>
You get C-state residency at the socket level with my perf uncore
patch.
This patch is just about helping with unbalance at the physical
core level.
> I think Cx could be added relatively easily as a software event,
> but frequency doesn't fit very well into the perf counting model,
> as it's really sampling.
>
> -Andi
prev parent reply other threads:[~2013-02-12 17:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 14:09 [PATCH 0/2] perf stat: add per-core count aggregation Stephane Eranian
2013-02-12 14:09 ` [PATCH 1/2] perf stat: refactor aggregation code Stephane Eranian
2013-02-12 17:26 ` Andi Kleen
2013-02-13 7:50 ` Namhyung Kim
2013-02-13 9:38 ` Stephane Eranian
2013-02-12 14:09 ` [PATCH 2/2] perf stat: add per-core aggregation Stephane Eranian
2013-02-12 17:23 ` [PATCH 0/2] perf stat: add per-core count aggregation Andi Kleen
2013-02-12 17:26 ` Stephane Eranian
2013-02-12 17:29 ` Andi Kleen
2013-02-12 17:33 ` Stephane Eranian [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='CABPqkBQBnN8y7WWWye1e0goJ6On1SYOKWsUG9=R76+d7ScWLDg@mail.gmail.com' \
--to=eranian@google.com \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung.kim@lge.com \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.