From: Frederic Weisbecker <fweisbec@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>, Kevin Hilman <khilman@linaro.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: [RFC PATCH 0/5] nohz: Move nohz kick out of scheduler IPI, v4
Date: Tue, 13 May 2014 16:38:36 +0200 [thread overview]
Message-ID: <1399991921-17618-1-git-send-email-fweisbec@gmail.com> (raw)
So this version now implements remote irq works using the generic IPI
interrupt available in most archs, as suggested by Peterz.
Keep in mind that the first patch is really just a draft to build the
mockup. It needs to be turned into an internal state set on boot or so.
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
timers/nohz-irq-work-v2
Thanks,
Frederic
---
Frederic Weisbecker (5):
irq_work: Let arch tell us if it can raise irq work
irq_work: Force non-lazy works to the IPI
irq_work: Allow remote queueing
nohz: Move full nohz kick to its own IPI
nohz: Use IPI implicit full barrier against rq->nr_running r/w
arch/alpha/kernel/time.c | 5 +++
arch/arm/kernel/smp.c | 5 +++
arch/powerpc/kernel/time.c | 5 +++
arch/sparc/kernel/pcr.c | 5 +++
arch/x86/kernel/irq_work.c | 7 ++++
include/linux/irq_work.h | 3 ++
include/linux/tick.h | 9 ++++-
kernel/irq_work.c | 83 +++++++++++++++++++++++++++++++---------------
kernel/sched/core.c | 14 ++++----
kernel/sched/sched.h | 12 +++++--
kernel/smp.c | 3 ++
kernel/time/tick-sched.c | 10 +++---
kernel/timer.c | 2 +-
13 files changed, 119 insertions(+), 44 deletions(-)
next reply other threads:[~2014-05-13 14:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 14:38 Frederic Weisbecker [this message]
2014-05-13 14:38 ` [PATCH 1/5] irq_work: Let arch tell us if it can raise irq work Frederic Weisbecker
2014-05-13 17:09 ` Peter Zijlstra
2014-05-13 19:33 ` Frederic Weisbecker
2014-05-13 20:48 ` Peter Zijlstra
2014-05-13 21:15 ` Frederic Weisbecker
2014-05-13 14:38 ` [PATCH 2/5] irq_work: Force non-lazy works to the IPI Frederic Weisbecker
2014-05-13 14:38 ` [PATCH 3/5] irq_work: Allow remote queueing Frederic Weisbecker
2014-05-13 14:38 ` [PATCH 4/5] nohz: Move full nohz kick to its own IPI Frederic Weisbecker
2014-05-13 14:38 ` [PATCH 5/5] nohz: Use IPI implicit full barrier against rq->nr_running r/w 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=1399991921-17618-1-git-send-email-fweisbec@gmail.com \
--to=fweisbec@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=khilman@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.org \
/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.