69e9f8638d
But certain logic interacts with tasks in different ways. The only one that comes to mind are wdogs. There is a tasking interface that to manipulate wdogs, and a different interface in the timer interrupt handling logic to manage wdog expirations. In the normal case, this is fine. Since the tasking level code calls enter_critical_section, interrupts are disabled an no conflicts can occur. But that may not be the case in the SMP case. Most architectures do not permit disabling interrupts on other CPUs so enter_critical_section must work differently: Locks are required to protect code. So this change adds locking (via enter_critical section) to wdog expiration logic for the the case if the SMP configuration. |
||
|---|---|---|
| .. | ||
| Make.defs | ||
| wd_cancel.c | ||
| wd_create.c | ||
| wd_delete.c | ||
| wd_gettime.c | ||
| wd_initialize.c | ||
| wd_recover.c | ||
| wd_start.c | ||
| wdog.h | ||