]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
projects / thirdparty / kernel / stable.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: b25f953) | patch
RISC-V: Upgrade smp_mb__after_spinlock() to iorw,iorw
authorPalmer Dabbelt <palmerdabbelt@google.com>
Thu, 16 Jul 2020 18:57:26 +0000 (11:57 -0700)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 29 Jul 2020 08:19:54 +0000 (10:19 +0200)
commitfcf756c2d796ebd29f7f180a2f5e4b272e38890f
tree22daedd8597833915d5e1e2e9e2144020a6568a8tree
parentb25f9539a646dbae22960dbb39226370ad477262commit | diff
RISC-V: Upgrade smp_mb__after_spinlock() to iorw,iorw

[ Upstream commit 38b7c2a3ffb1fce8358ddc6006cfe5c038ff9963 ]

While digging through the recent mmiowb preemption issue it came up that
we aren't actually preventing IO from crossing a scheduling boundary.
While it's a bit ugly to overload smp_mb__after_spinlock() with this
behavior, it's what PowerPC is doing so there's some precedent.

Signed-off-by: Palmer Dabbelt <palmerdabbelt@google.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
arch/riscv/include/asm/barrier.h diff | blob | blame | history
Mirror https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git