aboutsummaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/proc.py
diff options
context:
space:
mode:
authorWill Deacon <[email protected]>2019-02-11 15:24:56 +0000
committerWill Deacon <[email protected]>2019-04-08 11:59:30 +0100
commit4614bbdee35706ed77c130d23f12e21479b670ff (patch)
tree71342b4d66d5f23bcfe7b3764237fe2c93cecfa7 /scripts/gdb/linux/proc.py
parent79a3aaa7b82e3106be97842dedfd8429248896e6 (diff)
docs/memory-barriers.txt: Rewrite "KERNEL I/O BARRIER EFFECTS" section
The "KERNEL I/O BARRIER EFFECTS" section of memory-barriers.txt is vague, x86-centric, out-of-date, incomplete and demonstrably incorrect in places. This is largely because I/O ordering is a horrible can of worms, but also because the document has stagnated as our understanding has evolved. Attempt to address some of that, by rewriting the section based on recent(-ish) discussions with Arnd, BenH and others. Maybe one day we'll find a way to formalise this stuff, but for now let's at least try to make the English easier to understand. Cc: Benjamin Herrenschmidt <[email protected]> Cc: Michael Ellerman <[email protected]> Cc: Arnd Bergmann <[email protected]> Cc: Peter Zijlstra <[email protected]> Cc: Andrea Parri <[email protected]> Cc: Palmer Dabbelt <[email protected]> Cc: Daniel Lustig <[email protected]> Cc: David Howells <[email protected]> Cc: Alan Stern <[email protected]> Cc: "Maciej W. Rozycki" <[email protected]> Cc: Mikulas Patocka <[email protected]> Acked-by: Linus Torvalds <[email protected]> Reviewed-by: Paul E. McKenney <[email protected]> Signed-off-by: Will Deacon <[email protected]>
Diffstat (limited to 'scripts/gdb/linux/proc.py')
0 files changed, 0 insertions, 0 deletions