[riot-notifications] [RIOT-OS/RIOT] fe310: Fix potential deadlock in thread_yield_higher (#15277)

Marian Buschsieweke notifications at github.com
Thu Jan 7 15:40:07 CET 2021


Note that the implementation right now is not a RISC-V implementation, but specific to the fe310. So far we can rightfully assume to have the exact behavior this MCU has (including the timing). Hence, WFI cannot be a `nop` and will be reached before the soft IRQ is triggered. So IMO there is no bug in the code.

That said, obviously we want to support more RISC-V MCUs in the future. Getting rid of code relying on the implementation details of a specific MCU would certainly be a step in the right direction.

Let me do an `elf_diff` to se if we can do something about the performance impact.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/15277#issuecomment-756156446
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20210107/6d78364b/attachment.htm>


More information about the notifications mailing list