linux-kernel - [PATCH 0/3] smp.h: !SMP cleanups.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri,  2 Aug 2013 14:09:33 -0700
From:	David Daney <ddaney.cavm@...il.com>
To:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Cc:	David Daney <david.daney@...ium.com>
Subject: [PATCH 0/3] smp.h: !SMP cleanups.

From: David Daney <david.daney@...ium.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/