Skip to content

[SYCL] Locks in the ProgramManager should be revisited #18165

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

Open
ianayl opened this issue Apr 23, 2025 · 0 comments
Open

[SYCL] Locks in the ProgramManager should be revisited #18165

ianayl opened this issue Apr 23, 2025 · 0 comments
Labels
enhancement New feature or request runtime Runtime library related issue

Comments

@ianayl
Copy link
Contributor

ianayl commented Apr 23, 2025

Locking in the ProgramManager should be revisited, as:

@ianayl ianayl added enhancement New feature or request runtime Runtime library related issue labels Apr 23, 2025
martygrant pushed a commit that referenced this issue Apr 24, 2025
#18121)

This PR guards accesses to `m_DeviceImage` and `m_VFSet2BinImage`
caches/maps in the Program Manager using `m_KernelIDsMutex` in
situations where multiple threads may be accessing the maps at the same
time.

I am opting to use `m_KernelIDsMutex` here as both maps are commonly
accessed while holding said mutex: In fact, a lot of maps/caches in the
program manager use `m_KernelIDsMutex` (This is not the most optimal
solution, but that is out of the scope of this PR, see #18165)

This PR addresses Coverity hits that needs to have fixes submitted
before the code cutoff.

---------

Co-authored-by: Steffen Larsen <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request runtime Runtime library related issue
Projects
None yet
Development

No branches or pull requests

1 participant