Open xuzihan351 opened 11 months ago
This is definitely possible... tx_thread_schedule.s, tx_thread_system_return.s, tx_thread_context_save.s, and tx_thread_context_restore.s are the likely places for the enhanced logic.
Did you find out any issues related to FPU when porting to RISC-V ?
No issues found at the moment
Not even this kind of https://github.com/eclipse-threadx/threadx/issues/389 ?
That is a bug, and I had fix it locally.
thanks you targeted a mpfs250 board?
Not that. I am targeting HPMicro series boards
RISCV has a FS filed in MSTATUS, it indicates the status of the fpu. It can be initial, clean, dirty of off. When dealing with the fpu context save and restore, the FS filed may help to increase the preformence of the context switching. When the MSTATUS.FS is clean or off, the context saving and restoring can be skip. Is it possible to implement this feature in the future?