sched: process scheduler before wd_timer handler

[zyfeier]

Summary

wd_timer handler will change current task, so need process scheduler before wd timer handler, Ensure that the current task is not updated before the RR process.

Impact

RR sched with tickless

Testing

Test with sabre-6quad, config CONFIG_RR_INTERVAL

[nuttxpr]

[Experimental Bot, please feedback here]

No, this PR does not meet the NuttX requirements.

Missing Information:

• Summary:
  • The "why" is not clear. Why is changing the task in the watchdog timer handler a problem?
  • What is the specific change being made to the code? Be explicit.
  • No related issue references provided.
• Impact:
  • Vague. Provide specific details for each impact category (e.g., which architectures, boards, or drivers are affected). Explain how the build process changes.
• Testing:
  • Incomplete.
    • Specify the host OS, CPU, and compiler used for testing.
    • Provide the full board:config used for testing on Sabre-6quad.
    • The testing logs are placeholders. Include actual logs demonstrating the problem before the change and the fix after the change.

Recommendations:

1. Elaborate on the problem: Clearly explain the issue caused by the watchdog timer handler changing the current task. Why is it necessary to run the scheduler before the watchdog timer handler? What are the consequences of not doing so?
2. Detail the solution: Describe the specific code changes you made to address the problem. How do your changes ensure the current task is not updated before the round-robin (RR) process?
3. Provide specific impact information: For each impact category, provide concrete details instead of general statements.
4. Complete the testing section: Replace the placeholders with:
   • The host OS, CPU, and compiler version used for testing.
   • The complete board:config used for testing on Sabre-6quad.
   • Actual testing logs demonstrating the problem before and the successful outcome after your changes.

By providing this missing information, your PR will be much clearer and easier for the NuttX maintainers to review.