patacongo commented on issue #802: URL: https://github.com/apache/incubator-nuttx/issues/802#issuecomment-617776554
> Maybe we can change up_interrupt_context to check the hardware status bit instead of CURRENT_REGS, then syslog can be called in any point, but it is another story. That might be much more compilicated than you think. You should study the probleml before jumping into an unnecessary, alternative solution. Nothing is broken. Whenever, up_interrupt_context() returns true, the code also assumes that CURRENT_REGS is non-NULL. That is the accepted semantics. Those two things cannot be easily separated. up_assert() is a good example. In the interrupt context, it needs the CURRENT_REGS. These are probably other less obvious dependences. Also, high priority, nested, zero latency interrupts worked very differently. They are not treated as interrupts at all. I think this is not a good idea. It is, at least, not something that you should do impulsively or without some significant analysis of the consequences. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
