aboutsummaryrefslogtreecommitdiff
path: root/kernel/spinlock.c
diff options
context:
space:
mode:
authorRobert Morris <rtm@csail.mit.edu>2019-07-11 05:41:59 -0400
committerRobert Morris <rtm@csail.mit.edu>2019-07-11 05:41:59 -0400
commit7797a384236cee31b924d27d8f814ef9543662cd (patch)
treec6222d9a40f9ce0bc9f589525d33e882f1670a6b /kernel/spinlock.c
parent4bc900e78bdbff3ba22ccccd26833cf70fd300b1 (diff)
downloadxv6-labs-2022-7797a384236cee31b924d27d8f814ef9543662cd.tar.xz
xv6-labs-2022-7797a384236cee31b924d27d8f814ef9543662cd.zip
another test, to help with locking exercises
Diffstat (limited to 'kernel/spinlock.c')
-rw-r--r--kernel/spinlock.c9
1 files changed, 5 insertions, 4 deletions
diff --git a/kernel/spinlock.c b/kernel/spinlock.c
index 52bd504..83512bb 100644
--- a/kernel/spinlock.c
+++ b/kernel/spinlock.c
@@ -25,7 +25,7 @@ acquire(struct spinlock *lk)
if(holding(lk))
panic("acquire");
- // On RISC-V, this turns into an atomic swap:
+ // On RISC-V, sync_lock_test_and_set turns into an atomic swap:
// a5 = 1
// s1 = &lk->locked
// amoswap.w.aq a5, a5, (s1)
@@ -57,9 +57,10 @@ release(struct spinlock *lk)
__sync_synchronize();
// Release the lock, equivalent to lk->locked = 0.
- // This code can't use a C assignment, since it might
- // not be atomic.
- // On RISC-V, this turns into an atomic swap:
+ // This code doesn't use a C assignment, since the C standard
+ // implies that an assignment might be implemented with
+ // multiple store instructions.
+ // On RISC-V, sync_lock_release turns into an atomic swap:
// s1 = &lk->locked
// amoswap.w zero, zero, (s1)
__sync_lock_release(&lk->locked);