max/embassy
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Work around xtensa deadlock, take 2

Browse Source
This commit is contained in:
Dániel Buga 2023-05-13 13:44:19 +02:00
parent 82f7e104d9
commit 5fe36b6bb0
1 changed files with 20 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
embassy-executor/src/arch/xtensa.rs
View File

@ -63,21 +63,29 @@ mod thread {
loop { loop {
unsafe { unsafe {
self.inner.poll(); self.inner.poll();
// Manual critical section implementation that only masks interrupts handlers.
// We must not acquire the cross-core on dual-core systems because that would
// prevent the other core from doing useful work while this core is sleeping.
let token: critical_section::RawRestoreState;
core::arch::asm!("rsil {0}, 5", out(reg) token);
// we do not care about race conditions between the load and store operations, interrupts // we do not care about race conditions between the load and store operations, interrupts
// will only set this value to true. // will only set this value to true.
// if there is work to do, loop back to polling // if there is work to do, loop back to polling
// TODO can we relax this? if SIGNAL_WORK_THREAD_MODE.load(Ordering::SeqCst) {
critical_section::with(|_| { SIGNAL_WORK_THREAD_MODE.store(false, Ordering::SeqCst);
if SIGNAL_WORK_THREAD_MODE.load(Ordering::SeqCst) {
SIGNAL_WORK_THREAD_MODE.store(false, Ordering::SeqCst); core::arch::asm!(
} else { "wsr.ps {0}",
// waiti sets the PS.INTLEVEL when slipping into sleep "rsync", in(reg) token)
// because critical sections in Xtensa are implemented via increasing } else {
// PS.INTLEVEL the critical section ends here // waiti sets the PS.INTLEVEL when slipping into sleep
// take care not add code after `waiti` if it needs to be inside the CS // because critical sections in Xtensa are implemented via increasing
core::arch::asm!("waiti 0"); // critical section ends here // PS.INTLEVEL the critical section ends here
} // take care not add code after `waiti` if it needs to be inside the CS
}); core::arch::asm!("waiti 0"); // critical section ends here
}
} }
} }
} }