ia64: Make sure that we have a mmiowb function real early
authorTony Luck <tony.luck@intel.com>
Thu, 16 May 2019 01:04:14 +0000 (18:04 -0700)
committerLinus Torvalds <torvalds@linux-foundation.org>
Thu, 16 May 2019 01:43:46 +0000 (18:43 -0700)
commit8a635ffb142125c6637fe71d5cbce25e7dfa275e
tree003d1b7af85af54a665b439ffa596e133b12c360
parent700a800a949467cb86491763b983e1edcdee8642
ia64: Make sure that we have a mmiowb function real early

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: 49ca6462fc9e ("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>
arch/ia64/kernel/machvec.c