MPFS boot enhancements

[eenurkka]

Summary

rmpfs IPI (Inter-processor Interrupts) are not cleared at boot currently. It's possible they're set at boot time, which then breaks the boot logic; harts1-4 should stay at wfi loop until they're released by an IPI.

In addition, clocks don't need to be reset if they're already set. Let the use configure whether the system clocks are already set or not.

Impact

If there's a chain of NuttX OS:es, for example, one NuttX that jumps to the next, the IPI fired at the 1st NuttX will make the follow-up NuttX proceed before it's released. Thus, clear the IPIs in like manner the interrupts are turned off at boot.

Testing

Various mpfs based products with more than one NuttX OSs following each other. The 1st one sets the clokcs, while the 2nd doesn't alter them.

[nuttxpr]

[Experimental Bot, please feedback here]

Yes, this PR appears to meet the NuttX requirements, although the Testing section could be improved.

Here's a breakdown:

• Summary: Clearly explains the problem (uncleared IPIs causing boot issues), the solution (clearing IPIs at boot, optional clock reset), and the rationale. It's concise and informative. A link to the related NuttX issue would strengthen it further.

• Impact: Adequately addresses the impact on users (potential boot issues in chained NuttX OS scenarios) and provides context. It lacks detail on other impact areas, especially regarding build process, hardware, documentation, security, and compatibility. While these might not be affected, explicitly stating "NO" for each with a brief justification ("No changes to build process," etc.) would enhance clarity and completeness.

• Testing: While it mentions the testing environment ("various mpfs based products"), it's lacking specific details. The NuttX requirements ask for build host details (OS, CPU, compiler) and target details (arch, board, config). Crucially, the "Testing logs before change" and "Testing logs after change" sections are empty. This is the weakest part of the PR description and needs significant improvement by including actual logs demonstrating the issue and the fix. Simply stating "works as intended" is insufficient.

Recommendation:

To fully meet the NuttX requirements, the PR should be updated to:

1. Summary: Include a link to the related NuttX issue if one exists.

2. Impact: Explicitly address all impact areas (build, hardware, documentation, security, compatibility) even if the impact is "NO." Provide brief justifications for each.

3. Testing: Provide detailed information about the build host and target environments. Include actual testing logs demonstrating the issue before the change and the corrected behavior after the change. These logs are crucial for reviewers to verify the fix.

[acassis]

@eenurkka I think you need to refresh some board configs, not sure, please look about the issue in rv_virt config

[xiaoxiang781216]

@eenurkka I think you need to refresh some board configs, not sure, please look about the issue in rv_virt config

it's a known ltp error on riscv, and not related to this patch.