leandrof/linux
1
0
Fork 0
forked from Minki/linux
Code Issues Pull Requests Packages Projects Releases Wiki Activity

ia64: Make sure that we have a mmiowb function real early

Browse Source 
Generic kernels feed many operation through the "machvec" logic to get
the correct form of the operation for the current system.  "mmiowb()" is
one of those operations.

Although machvec is initialized very early in boot, it isn't early
enough for a recent upstream kernel change that added mmiowb to the
spin_unlock() path.

Statically initialize the mmiowb field of machvec so that we won't die
with a call through a NULL pointer.  This should be safe because we do
the real initialization of machvec before bringing up any addtional CPUs
or doing any I/O.

Fixes: 49ca6462fc ("ia64/mmiowb: Add unconditional mmiowb() to arch_spin_unlock()")
Signed-off-by: Tony Luck <tony.luck@intel.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
Tony Luck 2019-05-15 18:04:14 -07:00 committed by Linus Torvalds
parent 700a800a94
commit 8a635ffb14
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
arch/ia64/kernel/machvec.c
View File

@ -10,7 +10,9 @@
#include <asm/page.h>
struct ia64_machine_vector ia64_mv;
struct ia64_machine_vector ia64_mv = {
.mmiowb = ___ia64_mmiowb
};
EXPORT_SYMBOL(ia64_mv);
static struct ia64_machine_vector * __init