You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently working on generating tests for a multicore setup, specifically aiming to create virtual tests. While I have successfully generated physical tests, I've encountered issues with generating virtual ones. The problem seems to arise during page table generation, where a page table is created for each hart but with the same section name in the .S file. This duplication leads to compilation errors.
My assumption is that there might not be existing support for this, so I'd like to ask if there are any plans to implement virtual test support for multicore configurations.
If this feature is not currently planned, I'd be interested in contributing to it myself, as I’ve already started working on a solution. I'd like to clarify a few details to make sure it aligns well with the project's direction. Let me know if you'd be open to discussing this!
Thanks for considering it!
The text was updated successfully, but these errors were encountered:
Hi!
I'm currently working on generating tests for a multicore setup, specifically aiming to create virtual tests. While I have successfully generated physical tests, I've encountered issues with generating virtual ones. The problem seems to arise during page table generation, where a page table is created for each hart but with the same section name in the .S file. This duplication leads to compilation errors.
My assumption is that there might not be existing support for this, so I'd like to ask if there are any plans to implement virtual test support for multicore configurations.
If this feature is not currently planned, I'd be interested in contributing to it myself, as I’ve already started working on a solution. I'd like to clarify a few details to make sure it aligns well with the project's direction. Let me know if you'd be open to discussing this!
Thanks for considering it!
The text was updated successfully, but these errors were encountered: