From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: rui.zhang@intel.com, rafael@kernel.org, daniel.lezcano@linaro.org
Cc: amitk@kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: [PATCH 0/4] Per CPU idle injection
Date: Mon, 7 Nov 2022 19:03:38 -0800 [thread overview]
Message-ID: <20221108030342.1127216-1-srinivas.pandruvada@linux.intel.com> (raw)
This series introduces per CPU idle injection. In preparation for this
enhance the existing powercap/idle_inject and modify intel_powerclamp
to use this. Then add per core idle injection driver.
Srinivas Pandruvada (4):
powercap: idle_inject: Export symbols
powercap: idle_inject: Add begin/end callbacks
thermal/drivers/intel_powerclamp: Use powercap idle-inject framework
thermal/drivers/intel_cpu_idle_cooling: Introduce Intel cpu idle
cooling driver
drivers/powercap/idle_inject.c | 26 +-
drivers/thermal/cpuidle_cooling.c | 2 +-
drivers/thermal/intel/Kconfig | 11 +
drivers/thermal/intel/Makefile | 1 +
.../thermal/intel/intel_cpu_idle_cooling.c | 262 ++++++++++++++++
drivers/thermal/intel/intel_powerclamp.c | 293 ++++++++----------
include/linux/idle_inject.h | 4 +-
7 files changed, 428 insertions(+), 171 deletions(-)
create mode 100644 drivers/thermal/intel/intel_cpu_idle_cooling.c
--
2.37.3
next reply other threads:[~2022-11-08 3:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 3:03 Srinivas Pandruvada [this message]
2022-11-08 3:03 ` [PATCH 1/4] powercap: idle_inject: Export symbols Srinivas Pandruvada
2022-11-08 3:03 ` [PATCH 2/4] powercap: idle_inject: Add begin/end callbacks Srinivas Pandruvada
2022-11-09 14:48 ` Rafael J. Wysocki
2022-11-10 23:13 ` srinivas pandruvada
2022-11-08 3:03 ` [PATCH 3/4] thermal/drivers/intel_powerclamp: Use powercap idle-inject framework Srinivas Pandruvada
2022-11-08 3:03 ` [PATCH 4/4] thermal/drivers/intel_cpu_idle_cooling: Introduce Intel cpu idle cooling driver Srinivas Pandruvada
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=20221108030342.1127216-1-srinivas.pandruvada@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rui.zhang@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;
as well as URLs for NNTP newsgroup(s).