hujun5 19b4911d7f arch: remove up_current_regs in common code ... reason: When entering an exception or interrupt, there are two sets of registers: one is the "running regs", which we need to save, and the other is the "ready to running regs", which we may soon use. For consistency in logic, we can always store the "running regs" in the regs field of g_running_tasks, otherwise it may lead to errors in the storage location of the "running regs." When we need to access the "running regs," we should uniformly retrieve them from the regs field of g_running_tasks. As the next step, we will rename the set_current_regs/up_current_regs functions for each architecture to more appropriate names, solely for the purpose of identifying interrupts. Signed-off-by: hujun5 <hujun5@xiaomi.com>		2024-11-15 18:25:35 +08:00
..
common	arch: fix the sched parameter update when exiting	2024-10-08 13:53:06 +08:00
mips32	arch: remove up_current_regs in common code	2024-11-15 18:25:35 +08:00
pic32mx	arch: remove up_current_regs in common code	2024-11-15 18:25:35 +08:00
pic32mz	arch: remove up_current_regs in common code	2024-11-15 18:25:35 +08:00
.gitignore	build: Remve the unnecessary .gitignore	2020-05-23 18:00:40 +01:00
Makefile	tools: Rename apps-or-nuttx-Make.defs to Make.defs	2024-10-17 07:55:02 +08:00