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>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Rusty Russell <rusty@rustcorp.com.au>,
Jacob Pan <jacob.jun.pan@linux.intel.com>
Subject: [PATCH v6 0/4] powercap/rapl: reduce ipi calls and misc clean up
Date: Wed, 24 Feb 2016 13:31:34 -0800 [thread overview]
Message-ID: <1456349498-1527-1-git-send-email-jacob.jun.pan@linux.intel.com> (raw)
Changes since v5:
- Split changes into seprate patches. No code change.
Changes since V4:
- Deleted unnecessary cpumask_any_and() call, assign first cpu as lead
Changes since V3:
- Avoid for_each_online_cpu() search for per package MSR access. This
is achieved by tracking a per package lead cpu via cpumask_xx() calls.
(suggested by Thomas Gleixner <tglx@linutronix.de>)
- Add direct reference of RAPL package for each RAPL domain.
Jacob Pan (4):
cpumask: export cpumask_any_but
powercap/rapl: reduce ipi calls
powercap/rapl: add package reference per domain
powercap/rapl: track lead cpu per package
drivers/powercap/intel_rapl.c | 220 ++++++++++++++++++++++--------------------
lib/cpumask.c | 1 +
2 files changed, 115 insertions(+), 106 deletions(-)
--
1.9.1
next reply other threads:[~2016-02-24 21:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 21:31 Jacob Pan [this message]
2016-02-24 21:31 ` [PATCH v6 1/4] cpumask: export cpumask_any_but Jacob Pan
2016-02-24 21:31 ` [PATCH v6 2/4] powercap/rapl: reduce ipi calls Jacob Pan
2016-02-24 21:31 ` [PATCH v6 3/4] powercap/rapl: add package reference per domain Jacob Pan
2016-02-24 21:31 ` [PATCH v6 4/4] powercap/rapl: track lead cpu per package Jacob Pan
2016-03-08 1:06 ` [PATCH v6 0/4] powercap/rapl: reduce ipi calls and misc clean up Jacob Pan
2016-03-08 7:57 ` Thomas Gleixner
2016-03-08 17:14 ` 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=1456349498-1527-1-git-send-email-jacob.jun.pan@linux.intel.com \
--to=jacob.jun.pan@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rusty@rustcorp.com.au \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).