Use the new atomic operations interface

Stick to a sequentially consistent model for most atomic operations as it
matches the semantics of the existing code. Each call site will have to be
reevaluated in order to switch to more relaxed accesses where possible.

1 files changed, 2 insertions, 2 deletions

diff --git a/kern/mutex.c b/kern/mutex.c
index 353d94a7..00077f26 100644
--- a/kern/mutex.c
+++ b/kern/mutex.c
@@ -34,7 +34,7 @@ mutex_lock_slow(struct mutex *mutex)
     sleepq = sleepq_lend(mutex, false, &flags);
 
     for (;;) {
-        state = atomic_swap_uint(&mutex->state, MUTEX_CONTENDED);
+        state = atomic_swap_seq_cst(&mutex->state, MUTEX_CONTENDED);
 
         if (state == MUTEX_UNLOCKED) {
             break;
@@ -44,7 +44,7 @@ mutex_lock_slow(struct mutex *mutex)
     }
 
     if (sleepq_empty(sleepq)) {
-        state = atomic_swap_uint(&mutex->state, MUTEX_LOCKED);
+        state = atomic_swap_seq_cst(&mutex->state, MUTEX_LOCKED);
         assert(state == MUTEX_CONTENDED);
     }