From: Frederic Weisbecker <fweisbec@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Alessio Igor Bogani <abogani@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Chris Metcalf <cmetcalf@tilera.com>,
Christoph Lameter <cl@linux.com>,
Geoff Levand <geoff@infradead.org>,
Gilad Ben Yossef <gilad@benyossef.com>,
Hakan Akkan <hakanakkan@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
Li Zhong <zhong@linux.vnet.ibm.com>,
Namhyung Kim <namhyung.kim@lge.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: [ANNOUNCE] 3.8-rc6-nohz4
Date: Wed, 6 Feb 2013 19:28:58 +0100 [thread overview]
Message-ID: <1360175338-6735-1-git-send-email-fweisbec@gmail.com> (raw)
Hi,
The support for printk and cputime accounting to work on full dynticks CPUs have
been merged in -tip tree and is likely deemed for the 3.9 merge window. So this
new release is a rebase against the relevant branches in -tip and v3.8-rc6.
The remaining amount of patches has thus quite schrinked.
You can pull this branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
3.8-rc6-nohz4
Remember it doesn't yet support everything the tick does, namely it lacks
full support for:
- Posix CPU timers
- Perf events
- sched_class::task_tick()
- various other scheduler details
- ...
So use it with caution!
Thanks.
PS: next upstream focus will probably be on posix cpu timers. May be we can try to
make it work using timer_list or hrtimers, I don't know yet. I need to experiment.
---
Changes since 3.8-rc4-nohz3 (including those of cputime):
* Rebase against v3.8-rc6 and latest tip:/sched/core and tip:/irq/core
* Fix cputime build error with kvm modules (Thanks Sedat Dilek and
Wu Fenguang)
* Fix cputime mistyped header inclusion in ia64
* Fix more missing symbols for kvm
* Removal of profiling's timer hook also applied in -tip
---
Frederic Weisbecker (26):
nohz: Basic full dynticks interface
nohz: Assign timekeeping duty to a non-full-nohz CPU
nohz: Trace timekeeping update
nohz: Wake up full dynticks CPUs when a timer gets enqueued
rcu: Restart the tick on non-responding full dynticks CPUs
sched: Comment on rq->clock correctness in ttwu_do_wakeup() in nohz
sched: Update rq clock on nohz CPU before migrating tasks
sched: Update rq clock on nohz CPU before setting fair group shares
sched: Update rq clock on tickless CPUs before calling
check_preempt_curr()
sched: Update rq clock earlier in unthrottle_cfs_rq
sched: Update clock of nohz busiest rq before balancing
sched: Update rq clock before idle balancing
sched: Update nohz rq clock before searching busiest group on load
balancing
nohz: Move nohz load balancer selection into idle logic
nohz: Full dynticks mode
nohz: Only stop the tick on RCU nocb CPUs
nohz: Don't turn off the tick if rcu needs it
nohz: Don't stop the tick if posix cpu timers are running
nohz: Add some tracing
rcu: Don't keep the tick for RCU while in userspace
timer: Don't run non-pinned timer to full dynticks CPUs
sched: Use an accessor to read rq clock
sched: Debug nohz rq clock
sched: Remove broken check for skip clock update
sched: Update rq clock before rt sched average scale
sched: Disable lb_bias feature for full dynticks
include/linux/posix-timers.h | 1 +
include/linux/rcupdate.h | 8 +++
include/linux/sched.h | 10 +++-
include/linux/tick.h | 9 +++
kernel/hrtimer.c | 3 +-
kernel/posix-cpu-timers.c | 11 ++++
kernel/rcutree.c | 19 +++++--
kernel/rcutree.h | 1 -
kernel/rcutree_plugin.h | 13 +---
kernel/sched/core.c | 104 ++++++++++++++++++++++++++++++---
kernel/sched/fair.c | 96 ++++++++++++++++++++++--------
kernel/sched/features.h | 3 +
kernel/sched/rt.c | 8 +-
kernel/sched/sched.h | 50 ++++++++++++++++
kernel/sched/stats.h | 8 +-
kernel/sched/stop_task.c | 8 +-
kernel/softirq.c | 5 +-
kernel/time/Kconfig | 9 +++
kernel/time/tick-broadcast.c | 3 +-
kernel/time/tick-common.c | 5 +-
kernel/time/tick-sched.c | 132 +++++++++++++++++++++++++++++++++++++----
kernel/timer.c | 5 +-
22 files changed, 427 insertions(+), 84 deletions(-)
--
1.7.5.4
next reply other threads:[~2013-02-06 18:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 18:28 Frederic Weisbecker [this message]
2013-02-07 2:50 ` Steven Rostedt
2013-02-07 11:10 ` Ingo Molnar
2013-02-07 15:41 ` Christoph Lameter
2013-02-07 16:12 ` Steven Rostedt
2013-02-07 16:30 ` Paul E. McKenney
2013-02-07 17:06 ` Steven Rostedt
2013-02-07 17:37 ` Paul E. McKenney
2013-02-07 16:25 ` Frederic Weisbecker
2013-02-07 16:41 ` Steven Rostedt
2013-02-07 16:45 ` Frederic Weisbecker
2013-02-07 17:03 ` Steven Rostedt
2013-02-07 17:45 ` Frederic Weisbecker
2013-02-07 19:07 ` Ingo Molnar
2013-02-07 19:19 ` Steven Rostedt
2013-02-08 15:51 ` Frederic Weisbecker
2013-02-11 9:59 ` Ingo Molnar
2013-02-07 16:41 ` Frederic Weisbecker
2013-02-07 17:00 ` Steven Rostedt
2013-02-07 17:18 ` Frederic Weisbecker
2013-02-07 19:14 ` Christoph Lameter
2013-02-07 19:55 ` Ingo Molnar
2013-02-08 6:18 ` Mike Galbraith
2013-02-08 15:53 ` Frederic Weisbecker
2013-02-08 16:18 ` Steven Rostedt
2013-02-08 16:24 ` Christoph Lameter
2013-02-08 18:57 ` Clark Williams
2013-02-08 19:43 ` Christoph Lameter
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=1360175338-6735-1-git-send-email-fweisbec@gmail.com \
--to=fweisbec@gmail.com \
--cc=abogani@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=cmetcalf@tilera.com \
--cc=geoff@infradead.org \
--cc=gilad@benyossef.com \
--cc=hakanakkan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=paul.gortmaker@windriver.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=zhong@linux.vnet.ibm.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
Powered by JetHome