sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update Changelog

Browse Source
This commit is contained in:
Gregory Nutt 2016-11-15 07:35:30 -06:00
parent a2531cea0c
commit e2f999a5df
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
configs/sabre-6quad/README.txt
View File

@ -498,6 +498,15 @@ Open Issues:
CPU (which may not be CPU0). Perhaps that should be a spinlock to prohibit CPU (which may not be CPU0). Perhaps that should be a spinlock to prohibit
execution of interrupts on CPU0 when other CPUs are in a critical section? execution of interrupts on CPU0 when other CPUs are in a critical section?
2016-11-15: When the critical section is used to lock a resource that is also
used by interupt handling, I believe that what is required is that the interrupt
handling logic must also take the spinlock. This will cause the interrupt handlers
on other CPUs to spin until leave_critical_section() is called.
NOTE: Currently enter_critical section takes the spinlock before disabling
(local) interrupts. That orderwould have to change or you could potentially get
deadlocks if the interrupt handler on the same CPU tries to take the spinlock.
2. Cache Concurency. This is a complex problem. There is logic in place now to 2. Cache Concurency. This is a complex problem. There is logic in place now to
clean CPU0 D-cache before starting a new CPU and for invalidating the D-Cache clean CPU0 D-cache before starting a new CPU and for invalidating the D-Cache
when the new CPU is started. REVISIT: Seems that this should not be necessary. when the new CPU is started. REVISIT: Seems that this should not be necessary.