Oopenvela-robotarch/smp: update g_running_tasks to percpu/g_running_task
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
Merge branch 'master' into vela apache/nuttx commit id: eb27ebba8adfe29644a7b890f86e6f16941921dc Signed-off-by: ligd <liguiding1@xiaomi.com> Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com> | 2 个月前 | |
Merge branch 'master' into vela apache/nuttx commit id: eb27ebba8adfe29644a7b890f86e6f16941921dc Signed-off-by: ligd <liguiding1@xiaomi.com> Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com> | 2 个月前 | |
arch/smp: update g_running_tasks to percpu/g_running_task If remove whole g_running_tasks, or replace it self as a macrro, will cause the gdb plugin not working. Signed-off-by: buxiasen <buxiasen@xiaomi.com> | 2 个月前 | |
Merge branch 'master' into vela apache/nuttx commit id: eb27ebba8adfe29644a7b890f86e6f16941921dc Signed-off-by: ligd <liguiding1@xiaomi.com> Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com> | 2 个月前 | |
riscv_syscall.S: Fix a massive bug in syscall dispatch logic There is an enormous error in the system call dispatch logic; if a task is inside a critical section (local interrupts disabled) there is a chance that during a context switch when the task resumes, local interrupts are erroneously ENABLED. This obviously leads to unexpected crashes and such. This happens when the CPU status has Previous Interrupt Enable (PIE) set to 1, even though Interrupt Enable (IE) is set to 0. When the system call returns via ERET, the CPU sets PIE->IE and if PIE=1 interrupts get enabled. This is fixed easily by explicitly CLEARING PIE from the register save area, if IE=0 when the system call was started. | 2 个月前 |