From: David Daney <ddaney.cavm@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Cc: David Daney <david.daney@cavium.com>
Subject: [PATCH 0/3] smp.h: !SMP cleanups.
Date: Fri, 2 Aug 2013 14:09:33 -0700 [thread overview]
Message-ID: <1375477776-13302-1-git-send-email-ddaney.cavm@gmail.com> (raw)
From: David Daney <david.daney@cavium.com>
This is a follow-on patch set to f21afc25f9 (smp.h: Use
local_irq_{save,restore}() in !SMP version of on_each_cpu().). There
are no problems known to me that are fixed, but it does make things more
consistent.
These are based on linux-next next-20130802 and the corresponding mm
patch series. And specifically akpm's
"include/linux/smp.h:on_each_cpu(): switch back to a C function"
patch.
The third patch (smp.h: Move !SMP version of on_each_cpu()
out-of-line) does seem to make the kernel slightly larger on some
architectures, so it is possible that it could be dropped if that
concerns people.
David Daney (3):
smp: Quit unconditionally enabling irq in on_each_cpu_mask and
on_each_cpu_cond
up.c: Use local_irq_{save,restore}() in smp_call_function_single.
smp.h: Move !SMP version of on_each_cpu() out-of-line
include/linux/smp.h | 83 ++++++++++++++---------------------------------------
kernel/up.c | 58 +++++++++++++++++++++++++++++++++++--
2 files changed, 76 insertions(+), 65 deletions(-)
--
1.7.11.7
next reply other threads:[~2013-08-02 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 21:09 David Daney [this message]
2013-08-02 21:09 ` [PATCH 1/3] smp: Quit unconditionally enabling irq in on_each_cpu_mask and on_each_cpu_cond David Daney
2013-08-02 21:09 ` [PATCH 2/3] up.c: Use local_irq_{save,restore}() in smp_call_function_single David Daney
2013-08-02 21:09 ` [PATCH 3/3] smp.h: Move !SMP version of on_each_cpu() out-of-line David Daney
2013-08-02 22:24 ` David Daney
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=1375477776-13302-1-git-send-email-ddaney.cavm@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david.daney@cavium.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox