Messages in this thread | | | Subject | Re: [PATCH v2 01/21] docs/memory-barriers.txt: Rewrite "KERNEL I/O BARRIER EFFECTS" section | From | Benjamin Herrenschmidt <> | Date | Fri, 12 Apr 2019 12:07:09 +1000 |
| |
On Thu, 2019-04-11 at 15:34 -0700, Linus Torvalds wrote: > On Thu, Apr 11, 2019 at 3:13 PM Benjamin Herrenschmidt > <benh@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?
Works for me, but why not spell all this out in the document ? We know, but others might not.
Cheers, Ben.
| |