summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorLaszlo Ersek <lersek@redhat.com>2015-04-27 13:32:35 +0200
committerMichael Tokarev <mjt@tls.msk.ru>2015-04-30 16:05:48 +0300
commitd3e4abdddfcf70b2e678de1c6b9b1c6cd3ce541e (patch)
tree49b7cab2b93d7f36d00839a8d900e72d64685815 /docs
parent5ecaa4ed882aa6040d2ddbfc6f487d8b4bcd3b83 (diff)
downloadqemu-d3e4abdddfcf70b2e678de1c6b9b1c6cd3ce541e.zip
docs/atomics.txt: fix two typos
Cc: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Laszlo Ersek <lersek@redhat.com> Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
Diffstat (limited to 'docs')
-rw-r--r--docs/atomics.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/atomics.txt b/docs/atomics.txt
index 6f2997bc65..ef285e3c2a 100644
--- a/docs/atomics.txt
+++ b/docs/atomics.txt
@@ -281,7 +281,7 @@ note that the other barrier may actually be in a driver that runs in
the guest!
For the purposes of pairing, smp_read_barrier_depends() and smp_rmb()
-both count as read barriers. A read barriers shall pair with a write
+both count as read barriers. A read barrier shall pair with a write
barrier or a full barrier; a write barrier shall pair with a read
barrier or a full barrier. A full barrier can pair with anything.
For example:
@@ -294,7 +294,7 @@ For example:
smp_rmb();
y = a;
-Note that the "writing" thread are accessing the variables in the
+Note that the "writing" thread is accessing the variables in the
opposite order as the "reading" thread. This is expected: stores
before the write barrier will normally match the loads after the
read barrier, and vice versa. The same is true for more than 2