All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: LKML <linux-kernel@vger.kernel.org>,
	Linux PM <linux-pm@vger.kernel.org>,
	Rafael Wysocki <rafael.j.wysocki@intel.com>
Cc: Len Brown <len.brown@intel.com>,
	Ajay Thomas <ajay.thomas.david.rajamanickam@intel.com>,
	Noor U Mubeen <noor.u.mubeen@intel.com>,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	Jacob Pan <jacob.jun.pan@linux.intel.com>
Subject: [PATCH v2 0/3] Intel RAPL updates for Atom CPUs
Date: Fri,  7 Nov 2014 09:29:24 -0800	[thread overview]
Message-ID: <1415381367-16693-1-git-send-email-jacob.jun.pan@linux.intel.com> (raw)

Running Average Power Limit (RAPL) is supported in Atom processors
with a slightly different implementation. This patchset abstracts the
differences and add support for newer ATOM CPUs.

Intel Software Developers Manual has also been updated with many changes
and clarifications on how RAPL units and power limits are calculated.

Changes:
	v2: fix 32 bit divide in time window calculation  

Jacob Pan (3):
  powercap/rapl: abstract per cpu type functions
  powercap/rapl: handle atom and core differences
  powercap/rapl: add new model ids

 drivers/powercap/intel_rapl.c | 264 ++++++++++++++++++++++++++++--------------
 1 file changed, 177 insertions(+), 87 deletions(-)

-- 
1.9.1


             reply	other threads:[~2014-11-07 17:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-07 17:29 Jacob Pan [this message]
2014-11-07 17:29 ` [PATCH v2 1/3] powercap/rapl: abstract per cpu type functions Jacob Pan
2014-11-07 17:29 ` [PATCH v2 2/3] powercap/rapl: handle atom and core differences Jacob Pan
2014-11-07 17:29 ` [PATCH v2 3/3] powercap/rapl: add new model ids Jacob Pan
2014-11-14 23:52 ` [PATCH v2 0/3] Intel RAPL updates for Atom CPUs Rafael J. Wysocki

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=1415381367-16693-1-git-send-email-jacob.jun.pan@linux.intel.com \
    --to=jacob.jun.pan@linux.intel.com \
    --cc=ajay.thomas.david.rajamanickam@intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=noor.u.mubeen@intel.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=srinivas.pandruvada@linux.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.