From: <cmetcalf@ezchip.com>
To: <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Andrew Morton <akpm@linux-foundation.org>,
Borislav Petkov <bp@alien8.de>,
Frederic Weisbecker <fweisbec@gmail.com>,
Gilad Ben-Yossef <gilad@benyossef.com>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>,
Kevin Hilman <khilman@linaro.org>,
Li Zhong <zhong@linux.vnet.ibm.com>,
Mike Galbraith <efault@gmx.de>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>, <netdev@vger.kernel.org>
Cc: Chris Metcalf <cmetcalf@ezchip.com>
Subject: [PATCH 0/4] initial NOHZ_FULL support for tile
Date: Tue, 24 Mar 2015 15:21:31 -0400 [thread overview]
Message-ID: <1427224895-30830-1-git-send-email-cmetcalf@ezchip.com> (raw)
From: Chris Metcalf <cmetcalf@ezchip.com>
These changes are the necessary minimum to make the tile architecture
work relatively well with NOHZ_FULL. The tile architecture has had
out-of-tree support since 2008 for a DATAPLANE mode that provided
similar functionality (called Zero-Overhead Linux in our marketing
materials); we are now in the process of layering that on top of the
community NOHZ_FULL to upstream it.
Chris Metcalf (4):
tile: support arch_irq_work_raise
tile: support CONTEXT_TRACKING and thus NOHZ_FULL
nohz: add tick_nohz_full_clear_cpus() API
net: tile: don't send interrupts to nohz cores by default
arch/tile/Kconfig | 1 +
arch/tile/include/asm/Kbuild | 1 -
arch/tile/include/asm/irq_work.h | 14 ++++++++++++++
arch/tile/include/asm/smp.h | 1 +
arch/tile/include/asm/thread_info.h | 9 ++++++---
arch/tile/kernel/process.c | 12 ++++++++----
arch/tile/kernel/ptrace.c | 22 ++++++++++++++++++++--
arch/tile/kernel/single_step.c | 3 +++
arch/tile/kernel/smp.c | 32 +++++++++++++++++++++++++++++++-
arch/tile/kernel/traps.c | 16 +++++++++-------
arch/tile/kernel/unaligned.c | 22 +++++++++++++---------
arch/tile/mm/fault.c | 10 +++++++---
drivers/net/ethernet/tile/tilegx.c | 5 ++++-
include/linux/tick.h | 7 +++++++
14 files changed, 124 insertions(+), 31 deletions(-)
create mode 100644 arch/tile/include/asm/irq_work.h
--
2.1.2
next reply other threads:[~2015-03-24 19:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 19:21 cmetcalf [this message]
2015-03-24 19:21 ` [PATCH 1/4] tile: support arch_irq_work_raise cmetcalf
2015-03-24 21:00 ` Frederic Weisbecker
2015-03-24 21:14 ` Peter Zijlstra
2015-03-24 22:06 ` Chris Metcalf
2015-03-25 8:03 ` Peter Zijlstra
2015-03-24 19:21 ` [PATCH 2/4] tile: support CONTEXT_TRACKING and thus NOHZ_FULL cmetcalf
2015-03-24 21:15 ` Frederic Weisbecker
2015-03-24 21:49 ` Chris Metcalf
2015-03-24 19:21 ` [PATCH 3/4] nohz: add tick_nohz_full_clear_cpus() API cmetcalf
2015-03-30 16:20 ` Chris Metcalf
2015-03-30 16:41 ` Rik van Riel
2015-03-30 16:45 ` Chris Metcalf
2015-03-24 19:21 ` [PATCH 4/4] net: tile: don't send interrupts to nohz cores by default cmetcalf
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=1427224895-30830-1-git-send-email-cmetcalf@ezchip.com \
--to=cmetcalf@ezchip.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=efault@gmx.de \
--cc=fweisbec@gmail.com \
--cc=gilad@benyossef.com \
--cc=hpa@zytor.com \
--cc=khilman@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--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
all inboxes | Powered by JetHome®