You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nuttx.apache.org by "anchao (via GitHub)" <gi...@apache.org> on 2026/10/20 05:21:31 UTC

[PR] sched/signal: disable POSIX timers when all signals are disabled [nuttx]

anchao opened a new pull request, #20826:
URL: https://github.com/apache/nuttx/pull/20826

   ## Summary                                                                      
                                                                                   
   Select `DISABLE_POSIX_TIMERS` when `DISABLE_ALL_SIGNALS` is enabled.            
                                                                                   
   `CONFIG_DISABLE_ALL_SIGNALS` removes the signal subsystem, but the current      
   POSIX timer implementation still depends on signal-based notification.          
                                                                                   
   In particular:                                                                  
                                                                                   
   - `timer_create()` defaults a `NULL` `sigevent` to `SIGEV_SIGNAL` with          
     `SIGALRM`.                                                                    
   - Timer expiration is delivered through `nxsig_notification()` with             
     `SI_TIMER`.                                                                   
   - `CONFIG_DISABLE_ALL_SIGNALS` intentionally omits signal subsystem             
     initialization.                                                               
                                                                                   
   Keeping POSIX timers enabled while all signal support is disabled leaves the    
   timer APIs wired to notification machinery that is intentionally unavailable.   
                                                                                   
   This change makes the Kconfig state match the no-signal configuration semantics 
   and avoids requiring every no-signal defconfig to manually disable POSIX timers.
                                                                                   
   ## Testing                                                                      
                                                                                   
   Tested with a local no-signal simulator configuration using:                    
                                                                                   
   ```sh                                                                           
   make distclean                                                                  
   ./tools/configure.sh -l sim:nsh                                     
   make -j$(nproc)                                                                 
   ```
   
   Also verified that the resulting configuration contains:
   ```
     CONFIG_DISABLE_ALL_SIGNALS=y                          
     CONFIG_DISABLE_POSIX_TIMERS=y                         
     # CONFIG_SCHED_WAITPID is not set                     
   ```


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] sched/signal: disable POSIX timers when all signals are disabled [nuttx]

Posted by "michallenc (via GitHub)" <gi...@apache.org>.
michallenc merged PR #20826:
URL: https://github.com/apache/nuttx/pull/20826


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] sched/signal: disable POSIX timers when all signals are disabled [nuttx]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #20826:
URL: https://github.com/apache/nuttx/pull/20826#issuecomment-6284120394

   <!-- membrowse-pr-comment -->
   ## <img src="https://membrowse.com/membrowse-logo.svg" height="24" align="top"> MemBrowse Memory Report &middot; [Explore what changed →](https://membrowse.com/public/apache/nuttx?commit_sha=50f03cd53d5173eb6354ed8660e1a756b7b9c9d7)
   
   
   *No memory changes detected for:*
   - [arduino-mega2560](https://membrowse.com/public/apache/nuttx/target/arduino-mega2560/compare?head=50f03cd53d5173eb6354ed8660e1a756b7b9c9d7&base=fa4e298e0fb2d1692c39207a3c851cc796fb6cad)
   - [esp32-devkitc](https://membrowse.com/public/apache/nuttx/target/esp32-devkitc/compare?head=50f03cd53d5173eb6354ed8660e1a756b7b9c9d7&base=fa4e298e0fb2d1692c39207a3c851cc796fb6cad)
   - [hifive1-revb](https://membrowse.com/public/apache/nuttx/target/hifive1-revb/compare?head=50f03cd53d5173eb6354ed8660e1a756b7b9c9d7&base=fa4e298e0fb2d1692c39207a3c851cc796fb6cad)
   - [mirtoo](https://membrowse.com/public/apache/nuttx/target/mirtoo/compare?head=50f03cd53d5173eb6354ed8660e1a756b7b9c9d7&base=fa4e298e0fb2d1692c39207a3c851cc796fb6cad)
   - [qemu-armv8a](https://membrowse.com/public/apache/nuttx/target/qemu-armv8a/compare?head=50f03cd53d5173eb6354ed8660e1a756b7b9c9d7&base=fa4e298e0fb2d1692c39207a3c851cc796fb6cad)
   - [qemu-intel64](https://membrowse.com/public/apache/nuttx/target/qemu-intel64/compare?head=50f03cd53d5173eb6354ed8660e1a756b7b9c9d7&base=fa4e298e0fb2d1692c39207a3c851cc796fb6cad)
   - [rx65n-rsk2mb](https://membrowse.com/public/apache/nuttx/target/rx65n-rsk2mb/compare?head=50f03cd53d5173eb6354ed8660e1a756b7b9c9d7&base=fa4e298e0fb2d1692c39207a3c851cc796fb6cad)
   - [s698pm-dkit](https://membrowse.com/public/apache/nuttx/target/s698pm-dkit/compare?head=50f03cd53d5173eb6354ed8660e1a756b7b9c9d7&base=fa4e298e0fb2d1692c39207a3c851cc796fb6cad)
   - [stm32-nucleo-f103rb](https://membrowse.com/public/apache/nuttx/target/stm32-nucleo-f103rb/compare?head=50f03cd53d5173eb6354ed8660e1a756b7b9c9d7&base=fa4e298e0fb2d1692c39207a3c851cc796fb6cad)
   
   ---
   <sub>Catch memory regressions in CI with [MemBrowse](https://membrowse.com). Free for open source.</sub>
   


-- 
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.

To unsubscribe, e-mail: commits-unsubscribe@nuttx.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org