smp_call_function_single(): be slightly less stupid
If you do smp_call_function_single(expression-with-side-effects, ...) then expression-with-side-effects never gets evaluated on UP builds. As always, implementing it in C is the correct thing to do. While we're there, uninline it for size and possible header dependency reasons. And create a new kernel/up.c, as a place in which to put uniprocessor-specific code and storage. It should mirror kernel/smp.c. Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Ingo Molnar <mingo@elte.hu>
This commit is contained in:
committed by
Ingo Molnar
parent
abede81c4f
commit
53ce3d9564
18
kernel/up.c
Normal file
18
kernel/up.c
Normal file
@ -0,0 +1,18 @@
|
||||
/*
|
||||
* Uniprocessor-only support functions. The counterpart to kernel/smp.c
|
||||
*/
|
||||
|
||||
#include <linux/kernel.h>
|
||||
#include <linux/module.h>
|
||||
#include <linux/smp.h>
|
||||
|
||||
int smp_call_function_single(int cpu, void (*func) (void *info), void *info,
|
||||
int wait)
|
||||
{
|
||||
WARN_ON(cpuid != 0);
|
||||
local_irq_disable();
|
||||
(func)(info);
|
||||
local_irq_enable();
|
||||
return 0;
|
||||
}
|
||||
EXPORT_SYMBOL(smp_call_function_single);
|
Reference in New Issue
Block a user