From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Oleg Nesterov <oleg@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: [GIT PULL] dynticks updates for 3.13
Date: Mon, 11 Nov 2013 15:49:47 +0100 [thread overview]
Message-ID: <1384181387-30194-1-git-send-email-fweisbec@gmail.com> (raw)
Ingo,
Please pull the timers/core branch that can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
timers/core
It passed through 0-day testing. I'm proposing it for 3.13 just in case but I'm ok
as well if you think it's too late and should be delayed for 3.14
Thanks,
Frederic
---
Frederic Weisbecker (5):
nohz: Convert a few places to use local per cpu accesses
context_tracking: Wrap static key check into more intuitive function name
context_tracking: Rename context_tracking_active() to context_tracking_cpu_is_enabled()
posix-timers: Spare workqueue if there is no full dynticks CPU to kick
posix-timers: Fix full dynticks CPUs kick on timer rescheduling
Paul Gortmaker (1):
trivial: fix spelling in CONTEXT_TRACKING_FORCE help text
include/linux/context_tracking.h | 10 ++++-----
include/linux/context_tracking_state.h | 11 +++++++---
include/linux/tick.h | 8 ++++----
include/linux/vtime.h | 4 ++--
init/Kconfig | 2 +-
kernel/context_tracking.c | 8 ++++----
kernel/posix-cpu-timers.c | 21 +++++++++----------
kernel/softirq.c | 4 +---
kernel/time/tick-broadcast.c | 6 +++---
kernel/time/tick-internal.h | 4 ++--
kernel/time/tick-sched.c | 37 ++++++++++++++--------------------
11 files changed, 54 insertions(+), 61 deletions(-)
next reply other threads:[~2013-11-11 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 14:49 Frederic Weisbecker [this message]
2013-11-30 13:59 ` Ingo Molnar
2013-11-30 14:11 ` Ingo Molnar
2013-12-02 14:39 ` Frederic Weisbecker
2013-12-02 14:48 ` Frederic Weisbecker
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=1384181387-30194-1-git-send-email-fweisbec@gmail.com \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=paul.gortmaker@windriver.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--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
all inboxes | Powered by JetHome®