-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Level Zero Sysman Backport for hwloc v2.11 #702
Comments
Hello. Do you need a proper release, or do you just need a v2.11 branch with those fixes? I am not planning to backport these intrusive changes to an official 2.11.3 but rather release a 2.12 (multiple hurdles have been delaying this release for dumb reasons but hopefully in a couple weeks). |
@bgoglin Its fine if you can include them in the v2.11 branch. We can adopt it in 2.12 whenever its available. |
I pushed a v2.11-mpich branch with 2.11.2 + all backported fixed pending in branch v2.11 + levelzero backports from v2.12. Can you test it? |
@bgoglin Thanks. It will take me a few weeks to integrate this into our build/testing at scale. So will take some time to report back. I will continue to use the v2.11-mpich branch until I can confirm that v2.12 works fine with mpich. |
It is ok to rebase this branch when I backport some changes in the official 2.11 ? Or would you rather get merges and fast-forward pulls? |
@bgoglin Rebase or whichever easier is fine. All I'm looking for is a branch/release which has the level zero fixes in hwloc and that works with MPICH. If v2.12 hwloc works with mpich then I wouldn't have to trouble you with maintaining this branch. |
Hi, It would be useful to back level zero fixes related to sysman to v2.11 branch. Since there is a dependency on this version and MPICH releases.
I did my best to backport the patches from master to v2.11 branch and tested it on Aurora.
Let me know if a PR on this is helpful or if there are other plans to backport these fixes.
https://github.com/servesh/hwloc/tree/v2.11-level-zero-fix
The text was updated successfully, but these errors were encountered: