From 4e8b3ebb8a92ba8c5f5aff6cdc65c84c280f1012 Mon Sep 17 00:00:00 2001 From: Gregory Nutt Date: Thu, 29 Nov 2018 12:50:29 -0600 Subject: [PATCH] Upate TODO list --- TODO | 21 +++++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-) diff --git a/TODO b/TODO index 047c193680..d573cea02d 100644 --- a/TODO +++ b/TODO @@ -1,4 +1,4 @@ -NuttX TODO List (Last updated November 10, 2018) +NuttX TODO List (Last updated November 29, 2018) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This file summarizes known NuttX bugs, limitations, inconsistencies with @@ -10,7 +10,7 @@ issues related to each board port. nuttx/: (15) Task/Scheduler (sched/) - (3) SMP + (4) SMP (1) Memory Management (mm/) (0) Power Management (drivers/pm) (3) Signals (sched/signal, arch/) @@ -499,6 +499,23 @@ o SMP simplification in the design and permit commonality with other, non-GIC implementations. + Title: ISSUES WITH ACCESSING CPU INDEX + Description: The CPU number is accessed usually with the macro this_cpu(). + The returned CPU number is then used for various things, + typically as an array index. However, if pre-emption is + not disabled,then it is possible that a context switch + could occur and that logic could run on anothe CPU with + possible fatal consequences. + + We need to evaluate all use of this_cpu() and assure that + it is used in a way that guarantees the the code continues + to execute on the same CPU. + + Status: Open + Prioity: Medium. This is a logical problem but I have nevers seen + an bugs caused by this. But I believe that failures are + possible. + o Memory Management (mm/) ^^^^^^^^^^^^^^^^^^^^^^^