[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [bug #50698] Need separate sys_arch functions for interrupt

From: Simon Goldschmidt
Subject: [lwip-devel] [bug #50698] Need separate sys_arch functions for interrupt context
Date: Thu, 4 Jan 2018 01:41:30 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0

Update of bug #50698 (project lwip):

                  Status:                    None => Wont Fix               
             Assigned to:                    None => goldsimon              
             Open/Closed:                    Open => Closed                 


Follow-up Comment #2:

Daniel, looking at this again I don't think it will work to adapt sys_arch to
- all code sections calling SYS_ARCH_PROTECT() would have to know if they are
in interrupt or not (at least the Cortex ports check that taskENTER_CRITICAL()
is not called from an ISR), and this is done from pbuf_alloc(), not only for
"free from other context"
- functions that call "fromISR" code would have to return the bool that
indicates if scheduling is required

I guess I'll implement an optional mechanism that keeps a global counter
"inISR" instead...


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]