Skip to content

v5.0.x common/ofi: Utilize new libfabric API to import memhooks monitor #9303

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

Merged
merged 1 commit into from
Aug 26, 2021

Conversation

wckzhang
Copy link
Contributor

This patch attempts to open up libfabric resources in order to notify
libfabric when our memhooks patcher intercepts free calls.

Signed-off-by: William Zhang [email protected]
(cherry picked from commit 25811e2)

This patch attempts to open up libfabric resources in order to notify
libfabric when our memhooks patcher intercepts free calls.

Signed-off-by: William Zhang <[email protected]>
(cherry picked from commit 25811e2)
@wckzhang
Copy link
Contributor Author

I still need to do the 4.1 branch cherry-pick, unfortunately I hit a segfault there so I likely have to fix something first

@awlauria
Copy link
Contributor

Does this fix #8822?

@wckzhang
Copy link
Contributor Author

wckzhang commented Aug 23, 2021

Yeah Austin, I mentioned it for the original patch, didn't end up mentioning it for the cherry-pick. This prevents us from trying to do memory patching twice.

@awlauria awlauria linked an issue Aug 23, 2021 that may be closed by this pull request
@wckzhang
Copy link
Contributor Author

Turns out the segfault is just occurring in the 4.1.x branch w/o my patch...that's not good

@gpaulsen gpaulsen merged commit aaef492 into open-mpi:v5.0.x Aug 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Memory patcher conflicts with OMPI and libfabric
3 participants