From: Frederic Weisbecker <fweisbec@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Catalin Iacob <iacobcatalin@gmail.com>,
Dave Jones <davej@redhat.com>, Ingo Molnar <mingo@kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: [RFC PATCH 0/9] nohz: Nohz full kick fixes
Date: Thu, 21 Aug 2014 16:52:48 +0200 [thread overview]
Message-ID: <1408632777-3348-1-git-send-email-fweisbec@gmail.com> (raw)
Hi,
There have been several reports of warnings and lockup lately due to
recent or longer term issues.
This patchset is a proposed solution to fix them.
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
nohz/fixes
Thanks,
Frederic
---
Frederic Weisbecker (9):
nohz: Restore NMI safe local irq work for local nohz kick
nohz: Move nohz full init call to tick init
irq_work: Force raised irq work to run on irq work interrupt
x86: Build irq work only if local apic support
x86: Tell irq work about self IPI support
arm: Tell irq work about self IPI support
arm64: Tell irq work about self IPI support
nohz: Consolidate nohz full init code
nohz: nohz full depends on irq work self IPI support
arch/arm/kernel/smp.c | 5 +++
arch/arm64/kernel/smp.c | 5 +++
arch/x86/Kconfig | 4 +++
arch/x86/include/asm/entry_arch.h | 2 +-
arch/x86/kernel/Makefile | 2 +-
arch/x86/kernel/entry_64.S | 2 +-
arch/x86/kernel/irq_work.c | 7 +++--
arch/x86/kernel/irqinit.c | 2 +-
include/linux/irq_work.h | 4 +++
include/linux/tick.h | 9 +-----
init/main.c | 2 +-
kernel/irq_work.c | 21 ++++++++++++-
kernel/time/tick-common.c | 1 +
kernel/time/tick-internal.h | 7 +++++
kernel/time/tick-sched.c | 66 ++++++++++++++++++++++++++++-----------
kernel/time/timer.c | 2 +-
16 files changed, 105 insertions(+), 36 deletions(-)
next reply other threads:[~2014-08-21 14:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 14:52 Frederic Weisbecker [this message]
2014-08-21 14:52 ` [RFC PATCH 1/9] nohz: Restore NMI safe local irq work for local nohz kick Frederic Weisbecker
2014-08-21 14:52 ` [RFC PATCH 2/9] nohz: Move nohz full init call to tick init Frederic Weisbecker
2014-08-21 14:52 ` [RFC PATCH 3/9] irq_work: Force raised irq work to run on irq work interrupt Frederic Weisbecker
2014-09-04 6:11 ` Peter Zijlstra
2014-09-04 13:33 ` Frederic Weisbecker
2014-09-04 15:40 ` Peter Zijlstra
2014-09-05 13:54 ` Frederic Weisbecker
2014-09-06 13:35 ` Frederic Weisbecker
2014-09-06 15:45 ` Peter Zijlstra
2014-09-06 17:12 ` Frederic Weisbecker
2014-09-08 6:11 ` Peter Zijlstra
2014-08-21 14:52 ` [RFC PATCH 4/9] x86: Build irq work only if local apic support Frederic Weisbecker
2014-08-21 14:52 ` [RFC PATCH 5/9] x86: Tell irq work about self IPI support Frederic Weisbecker
2014-08-21 14:52 ` [RFC PATCH 6/9] arm: " Frederic Weisbecker
2014-08-21 15:21 ` Russell King - ARM Linux
2014-08-21 17:35 ` Frederic Weisbecker
2014-08-21 14:52 ` [RFC PATCH 7/9] arm64: " Frederic Weisbecker
2014-08-21 14:52 ` [RFC PATCH 8/9] nohz: Consolidate nohz full init code Frederic Weisbecker
2014-08-21 14:52 ` [RFC PATCH 9/9] nohz: nohz full depends on irq work self IPI support 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=1408632777-3348-1-git-send-email-fweisbec@gmail.com \
--to=fweisbec@gmail.com \
--cc=davej@redhat.com \
--cc=iacobcatalin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.