sched/signal: Simplified Implementation for SIGEV_THREAD_TID

[Fix-Point]

Summary

This commit simplified the implementation for SIGEV_THREAD_TID and added the missing siginfo initializer.

Impact

POSIX timer with SIGEV_THREAD_TID flag.

Testing

Tested on QEMU using rt-tests/cyclictest.

[lupyuen]

[Experimental Bot, please feedback here]

No, this PR does not meet the NuttX requirements.

Here's why:

• Insufficient Summary:

  • The summary is too brief. While it mentions the changes made, it lacks crucial details about why these changes were necessary. Was there a bug? Did the previous implementation have limitations?
  • It doesn't specify which functional part of the code is affected. Is it related to the kernel, a specific driver, or a library?

• Incomplete Impact Assessment:

  • Feature Addition/Change: The impact section vaguely states "POSIX timer with SIGEV_THREAD_TID flag." Be explicit. Is this a new feature? If so, describe its functionality. If it's a change, explain how the existing feature is impacted.
  • Other Impacts: The PR only addresses impact on users, leaving other aspects like build process, hardware, documentation, security, and compatibility completely unaddressed. Even for user impact, it lacks specifics. How will users interact with this new/modified feature?

• Insufficient Testing Details:

  • Limited Testing Environment: The PR only mentions testing on QEMU. Specify the QEMU version and the specific architecture being emulated. Ideally, testing should be done on real hardware as well, if possible.
  • Missing Build Host Information: Details about the build host are entirely missing. This includes the operating system, CPU architecture, and the compiler used (including the version).
  • Absent Testing Logs: The PR provides placeholders for testing logs instead of the actual logs. This makes it impossible to verify the claimed functionality or identify potential issues.

To improve this PR:

1. Expand the Summary: Explain the rationale behind the changes. Mention the specific code sections (files, functions) that were modified. If applicable, link to a relevant NuttX issue.
2. Thoroughly Address Impact: Analyze and describe the impact on all the listed aspects (build, hardware, documentation, security, compatibility). Be specific about how each area is affected.
3. Provide Comprehensive Testing Information:
   • List all build host environments used, including OS, CPU, and compiler details.
   • Mention the specific QEMU version and the emulated architecture.
   • Include actual testing logs from both before and after the changes.
   • If feasible, add testing results from real hardware platforms.

[xiaoxiang781216]

@Fix-Point let's revert the commit 9a9d0a6 too.