From: Ingo Molnar <mingo@kernel.org>
To: Vince Weaver <vince@deater.net>
Cc: Stephane Eranian <eranian@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"mingo@elte.hu" <mingo@elte.hu>,
"ak@linux.intel.com" <ak@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Jiri Olsa <jolsa@redhat.com>,
"Yan, Zheng" <zheng.z.yan@intel.com>,
Borislav Petkov <bp@alien8.de>,
Maria Dimakopoulou <maria.n.dimakopoulou@gmail.com>
Subject: Re: [PATCH v7 3/4] perf,x86: add Intel RAPL PMU support
Date: Thu, 28 Nov 2013 13:26:19 +0100 [thread overview]
Message-ID: <20131128122619.GA6561@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1311271653280.24499@pianoman.cluster.toy>
* Vince Weaver <vince@deater.net> wrote:
> On Wed, 27 Nov 2013, Stephane Eranian wrote:
>
> > On Wed, Nov 27, 2013 at 7:35 PM, Vince Weaver <vince@deater.net> wrote:
>
> > > So I notice PP1 (which is the GPU power on non-server chips)
> > > is not supported.
> > >
> > > Is that just for simplicity?
> > >
> > Does it work on specific models only? I bet so. How to detect those?
>
> In general it is on the machines that don't support the DRAM measurements
> (so the non-EP machines) but I don't know if there's a nice list anywhere.
>
> Intel manuals say:
> For a client platform, PP1 domain refers to the power plane of a
> specific device in the uncore. For server platforms, PP1 domain is not
> supported,
>
> usually PP1 I think maps to the embedded GPU.
It would indeed be nice to expose PP1 too via the same facility -
Haswell and later spends some 40% of the CPU die on the integrated GPU
and people end up using it.
Thanks,
Ingo
next prev parent reply other threads:[~2013-11-28 12:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 16:58 [PATCH v7 0/4] perf/x86: add Intel RAPL PMU support Stephane Eranian
2013-11-12 16:58 ` [PATCH v7 1/4] perf: add active_entry list head to struct perf_event Stephane Eranian
2013-11-27 14:07 ` [tip:perf/core] perf: Add " tip-bot for Stephane Eranian
2013-11-12 16:58 ` [PATCH v7 2/4] perf stat: add event unit and scale support Stephane Eranian
2013-11-27 14:08 ` [tip:perf/core] tools/perf/stat: Add " tip-bot for Stephane Eranian
2013-11-12 16:58 ` [PATCH v7 3/4] perf,x86: add Intel RAPL PMU support Stephane Eranian
2013-11-27 10:23 ` Peter Zijlstra
2013-11-27 14:08 ` [tip:perf/core] perf/x86: Add " tip-bot for Stephane Eranian
2013-11-27 18:35 ` [PATCH v7 3/4] perf,x86: add " Vince Weaver
2013-11-27 18:38 ` Stephane Eranian
2013-11-27 22:03 ` Vince Weaver
2013-11-28 12:26 ` Ingo Molnar [this message]
2013-11-28 12:35 ` Stephane Eranian
2013-11-29 19:16 ` Vince Weaver
2013-11-29 20:09 ` Stephane Eranian
2013-11-29 20:31 ` Borislav Petkov
2013-11-29 23:25 ` Stephane Eranian
2013-11-30 16:39 ` Vince Weaver
2013-11-12 16:58 ` [PATCH v7 4/4] perf,x86: add RAPL hrtimer support Stephane Eranian
2013-11-27 14:10 ` [tip:perf/core] perf/x86: Add " tip-bot for Stephane Eranian
2013-11-27 14:33 ` tip-bot for Stephane Eranian
2013-11-12 18:10 ` [PATCH v7 0/4] perf/x86: add Intel RAPL PMU support Andi Kleen
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=20131128122619.GA6561@gmail.com \
--to=mingo@kernel.org \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=bp@alien8.de \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maria.n.dimakopoulou@gmail.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=vince@deater.net \
--cc=zheng.z.yan@intel.com \
/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.