diff options
| author | Emilio G. Cota <cota@braap.org> | 2016-05-24 16:06:12 -0400 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2016-05-29 09:11:11 +0200 |
| commit | 56ebe02203f033a8399f7f6ea6972225ed87101c (patch) | |
| tree | de17c1e0e38cd4072b4b78be0431d750e201d437 /scripts/dump-guest-memory.py | |
| parent | 141af038dd1e73ed32e473046adeb822537c1152 (diff) | |
| download | focaccia-qemu-56ebe02203f033a8399f7f6ea6972225ed87101c.tar.gz focaccia-qemu-56ebe02203f033a8399f7f6ea6972225ed87101c.zip | |
docs/atomics: update atomic_read/set comparison with Linux
Recently Linux did a mass conversion of its atomic_read/set calls
so that they at least are READ/WRITE_ONCE. See Linux's commit
62e8a325 ("atomic, arch: Audit atomic_{read,set}()"). It seems though
that their documentation hasn't been updated to reflect this.
The appended updates our documentation to reflect the change, which
means there is effectively no difference between our atomic_read/set
and the current Linux implementation.
While at it, fix the statement that a barrier is implied by
atomic_read/set, which is incorrect. Volatile/atomic semantics prevent
transformations pertaining the variable they apply to; this, however,
has no effect on surrounding statements like barriers do. For more
details on this, see:
https://gcc.gnu.org/onlinedocs/gcc/Volatiles.html
Signed-off-by: Emilio G. Cota <cota@braap.org>
Message-Id: <1464120374-8950-2-git-send-email-cota@braap.org>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'scripts/dump-guest-memory.py')
0 files changed, 0 insertions, 0 deletions