linux-kernel - Re: [PATCH] kernel/cpu.c: create a CPU_STARTING cpu

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 8 Sep 2008 19:26:02 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Manfred Spraul <manfred@...orfullife.com>,
	"David S. Miller" <davem@...emloft.net>
Cc:	paulmck@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kernel/cpu.c: create a CPU_STARTING cpu_chain notifier


* Manfred Spraul <manfred@...orfullife.com> wrote:

> Right now, there is no notifier that is called on a new cpu, before 
> the new cpu begins processing interrupts/softirqs. Various kernel 
> function would need that notification, e.g. kvm works around by 
> calling smp_call_function_single(), rcu polls cpu_online_map.
> 
> The patch adds a CPU_STARTING notification. It also adds a helper 
> function that sends the message to all cpu_chain handlers.
> 
> Tested on x86-64.
>
> All other archs are untested. Especially on sparc, I'm not sure if I 
> got it right.

applied to tip/sched/cpu-hotplug - thanks Manfred, nice cleanup. (FYI, i 
fixed up the 3 problems that checkpatch reported)

David, can you see any problems with the Sparc32 bits?

	Ingo
--
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/