On Thu, Apr 11, 2019 at 3:13 PM Benjamin Herrenschmidt <b...@kernel.crashing.org> wrote: > > Minor nit... I would have said "All readX() and writeX() accesses _from > the same CPU_ to the same peripheral... and then s/the CPU/this CPU.
Maybe talk about "same thread" rather than "same cpu", with the
understanding that scheduling/preemption has to include the
appropriate cross-CPU IO barrier?
Linus
