mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, ak@linux.intel.com,
	acme@redhat.com, jolsa@redhat.com, zheng.z.yan@intel.com,
	bp@alien8.de, vincent.weaver@maine.edu,
	maria.n.dimakopoulou@gmail.com
Subject: Re: [PATCH v2 0/2] perf/x86: various RAPL improvements and fixes
Date: Wed, 8 Jan 2014 12:28:32 +0100	[thread overview]
Message-ID: <20140108112832.GB31570@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1389176153-3128-1-git-send-email-eranian@google.com>

On Wed, Jan 08, 2014 at 11:15:51AM +0100, Stephane Eranian wrote:
> This short patch series provides the following improvements
> to the RAPL support for perf_events:
>  - support for RAPL PP1 energy counter
>  - fix struct perf_event active_list field initialization
> 
> The PP1 counter maps to the builtin graphic card for client
> processors. that is why it is called energy-gpu.
> 
> The new energy event is:
>  - name: power/energy-gpu/
>  - code: 0x4
>  - unit: Joules
>  - scaling factor: 2^-32 Joules.
> 
> In v2, we renamed energy-pp1 to energy-gpu. We dropped the Haswell
> Celeron patch because it is committed already. But we add a fix for
> the broken initialization of the active_entry list.
> 

Thanks!

      parent reply	other threads:[~2014-01-08 11:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08 10:15 Stephane Eranian
2014-01-08 10:15 ` [PATCH v2 1/2] perf/x86: fix active_entry initialization Stephane Eranian
2014-01-12 18:42   ` [tip:perf/core] perf/x86: Fix " tip-bot for Stephane Eranian
2014-01-13 15:45     ` Peter Zijlstra
2014-01-13 15:49       ` Stephane Eranian
2014-01-08 10:15 ` [PATCH v2 2/2] perf/x86: add RAPL PP1 energy counter support Stephane Eranian
2014-01-12 18:42   ` [tip:perf/core] perf/x86/intel: Add Intel " tip-bot for Stephane Eranian
2014-01-08 11:28 ` Peter Zijlstra [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=20140108112832.GB31570@twins.programming.kicks-ass.net \
    --to=peterz@infradead.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=vincent.weaver@maine.edu \
    --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 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®