sched: replace up_cpu_index with this_cpu

[hujun260]

Summary

sched: replace up_cpu_index with this_cpu
Make this_cpu is arch independent and up_cpu_index do that. In AMP mode, up_cpu_index() may return the index of the physical core.

Impact

sched

Testing

ci ostest

[nuttxpr]

[Experimental Bot, please feedback here]

No. This PR description lacks crucial information required by the NuttX guidelines.

Here's why:

• Insufficient Summary: While it mentions the change (up_cpu_index to this_cpu), it doesn't clearly explain why this change is necessary. What problem does it solve? What are the benefits of using this_cpu? It also doesn't explain how the change works beyond a very high-level description.
• Incomplete Impact Assessment: Simply stating "sched" isn't enough. It needs YES/NO answers for all impact categories, with explanations where applicable. For example:
  • Impact on user: Likely NO, but needs confirmation.
  • Impact on build: Possibly NO, but needs explicit confirmation.
  • Impact on hardware: This is the most crucial part! The summary mentions AMP, implying a hardware impact. This needs a detailed explanation of which architectures/boards are affected.
  • Impact on documentation: Does this change require documentation updates?
  • Impact on security, compatibility: These need explicit NO/YES answers with justification.
• Inadequate Testing: "ci ostest" is not sufficient. It needs:
  • Specific build host details (OS, CPU, compiler versions).
  • Specific target details (architecture, board, configuration).
  • Actual testing logs before and after the change, demonstrating the issue and the fix. Empty code blocks are unacceptable.

The submitter needs to significantly revise this PR description to meet NuttX requirements before it can be properly reviewed.