Signed-off-by: SeongJae Park <sj38.park@xxxxxxxxx>
---
appendix/whymb/whymemorybarriers.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/appendix/whymb/whymemorybarriers.tex b/appendix/whymb/whymemorybarriers.tex
index 9002047a9878..3a22e46beb0c 100644
--- a/appendix/whymb/whymemorybarriers.tex
+++ b/appendix/whymb/whymemorybarriers.tex
@@ -2265,7 +2265,7 @@ a write to a given MMIO register affects the value that will next be
read from {\em some other} MMIO register.
It is not clear why SPARC does not define \co{wmb()} to be
-\co{membar #MemIssue} and \co{smb_wmb()} to be
+\co{membar #MemIssue} and \co{smp_wmb()} to be
\co{membar #StoreStore},
as the current definitions seem vulnerable to bugs in some drivers.
It is quite possible that all the SPARC CPUs that Linux runs on
--
2.10.0
--
To unsubscribe from this list: send the line "unsubscribe perfbook" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
