From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Len Brown <lenb@kernel.org>,
Rafael Wysocki <rafael.j.wysocki@intel.com>,
Eduardo Valentin <edubezval@gmail.com>,
Zhang Rui <rui.zhang@intel.com>, Petr Mladek <pmladek@suse.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Jacob Pan <jacob.jun.pan@linux.intel.com>
Subject: [PATCH v4 0/2] Stop sched tick in idle injection task
Date: Mon, 28 Nov 2016 13:33:27 -0800 [thread overview]
Message-ID: <1480368809-23685-1-git-send-email-jacob.jun.pan@linux.intel.com> (raw)
Changelog:
v4: - Misc comments from Ingo are addressed, including style fix,
timeout handling, fork().
- Dropped powerclamp patch from this set, move to its own
series.
v3: - Rearrange idle.c change based on Rafael's suggestion.
v2:
- Moved duration timer from powerclamp driver to play_idle()
- Unexport cpuidle_use_deepest_state
- Indentation fix
Idle injection drivers today use RT threads to run idle loop. There are
efficiency and accounting issues with the current intel_powerclamp.c
and acpi_pad.c. A while ago, I posted CFS based idle injection patch trying
to address them:
https://lkml.org/lkml/2015/11/13/576
Peter proposed another approach with the introduction of a PF_IDLE flag.
This patchset is based on his original posting:
https://lkml.org/lkml/2014/6/4/56
These patches apply on top of the kworker and cpu hotplug state machine
changes made to Intel powerclamp driver.
https://lkml.org/lkml/2016/10/17/362
Similar changes to ACPI PAD driver is developed along with other
enhancements. It will be posted after this patchset is accepted.
Jacob Pan (1):
cpuidle: allow setting deepest idle
Peter Zijlstra (1):
idle: add support for tasks that inject idle
drivers/cpuidle/cpuidle.c | 11 +++
include/linux/cpu.h | 2 +
include/linux/cpuidle.h | 4 +-
include/linux/sched.h | 3 +-
kernel/fork.c | 2 +-
kernel/sched/core.c | 1 +
kernel/sched/idle.c | 175 +++++++++++++++++++++++++++++-----------------
7 files changed, 129 insertions(+), 69 deletions(-)
--
1.9.1
next reply other threads:[~2016-11-28 21:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 21:33 Jacob Pan [this message]
2016-11-28 21:33 ` [PATCH v4 1/2] idle: add support for tasks that inject idle Jacob Pan
2016-11-28 21:39 ` Rafael J. Wysocki
2016-11-28 21:46 ` Jacob Pan
2016-11-28 22:22 ` Rafael J. Wysocki
2016-11-28 23:18 ` kbuild test robot
2016-11-28 23:22 ` Rafael J. Wysocki
2016-11-29 0:33 ` Jacob Pan
2016-11-29 0:39 ` Jacob Pan
2016-11-29 0:45 ` Rafael J. Wysocki
2016-11-28 21:33 ` [PATCH v4 2/2] cpuidle: allow setting deepest idle Jacob Pan
2016-11-28 23:12 ` kbuild test robot
2016-11-28 23:19 ` Rafael J. Wysocki
2016-11-29 0:59 ` kbuild test robot
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=1480368809-23685-1-git-send-email-jacob.jun.pan@linux.intel.com \
--to=jacob.jun.pan@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=edubezval@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rui.zhang@intel.com \
--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).