]> git.baikalelectronics.ru Git - kernel.git/commit
docs/memory-barriers.txt: Update I/O section to be clearer about CPU vs thread
authorWill Deacon <will.deacon@arm.com>
Fri, 12 Apr 2019 12:42:18 +0000 (13:42 +0100)
committerWill Deacon <will.deacon@arm.com>
Tue, 23 Apr 2019 12:34:17 +0000 (13:34 +0100)
commit377133515b2a84423f9cdff0fa1c01134033ad7b
tree89db071594101bfbfbd70ac1cf7fca4f6d3ca47e
parent87fa73fd6e82ecda8c58a1a2a3752c253827a1af
docs/memory-barriers.txt: Update I/O section to be clearer about CPU vs thread

The revised I/O ordering section of memory-barriers.txt introduced in
09da421de041 ("docs/memory-barriers.txt: Rewrite "KERNEL I/O BARRIER
EFFECTS" section") loosely refers to "the CPU", whereas the ordering
guarantees generally apply within a thread of execution that can migrate
between cores, with the scheduler providing the relevant barrier
semantics.

Reword the section to refer to "CPU thread" and call out ordering of
MMIO writes separately from ordering of writes to memory. Ben also
spotted that the string accessors are native-endian, so fix that up too.

Link: https://lkml.kernel.org/r/080d1ec73e3e29d6ffeeeb50b39b613da28afb37.camel@kernel.crashing.org
Fixes: 09da421de041 ("docs/memory-barriers.txt: Rewrite "KERNEL I/O BARRIER EFFECTS" section")
Reported-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Will Deacon <will.deacon@arm.com>
Documentation/memory-barriers.txt