arch/x86_64: Fix SMP startup for ACRN Hypervisor

[Fix-Point]

Summary

This patch fixed SMP startup for ACRN Hypervisor.

Impact

x86_64 SMP startup.

Testing

Tested on NUC12 ACRN hypervisor and QEMU/KVM x86_64.

[nuttxpr]

[Experimental Bot, please feedback here]

No, the PR does not meet the NuttX requirements.

Here's why and how to improve it:

• Insufficient Detail: The provided information is too brief and lacks the necessary specifics.
• Missing Information: Several sections are entirely missing, making it impossible to assess the PR's impact fully.

How to Improve the PR:

Summary:

• Why? Explain the root cause of the SMP startup issue on ACRN Hypervisor.
• What? Specify the code modules modified (e.g., architecture-specific startup code, scheduler, etc.).
• How? Describe the technical implementation of your fix (e.g., synchronization mechanism added, timing adjustment, etc.).
• Links: If applicable, provide links to related NuttX issues this PR addresses.

Impact:

• New Feature? NO (this is a bug fix).
• Existing Feature Changed? YES - x86_64 SMP startup
• User Impact: Likely NO (unless users were relying on the broken behavior, which is unlikely).
• Build Impact: Possibly YES if build flags or dependencies are affected. Describe any changes.
• Hardware Impact: YES - Specifically targets x86_64 systems running the ACRN Hypervisor.
• Documentation Impact: Possibly YES. If the fix involves user-facing behavior, documentation updates might be needed.
• Security Impact: Potentially YES. SMP issues can sometimes have security implications. Analyze and explain if this fix impacts security.
• Compatibility Impact: Possibly YES. Determine if this fix introduces any backward or forward compatibility issues.

Testing:

• Be Specific:
  • List the exact host operating systems, CPUs, and compiler versions used for testing.
  • Provide details on the specific ACRN Hypervisor version and QEMU/KVM configurations.
• Show, Don't Tell: Include relevant snippets from your testing logs. Demonstrate:
  • Evidence of the issue before the fix.
  • Successful SMP startup after the fix.

Remember: A well-written PR makes it easy for reviewers to understand your changes and their impact, significantly increasing the chances of a swift and successful merge.

[xiaoxiang781216]

let's ignore ci check error which is fixed by #14176 to avoid wasting github resources.