oneapi-src / oneapi-src/unified-runtime
Support for proxy layers in loader-only functions
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 57
- Forks
- 120
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 1
Description
The layers in the loader are essentially adapters that wrap the underlying implementation to provide additional functionality, be it validation, tracing, or something else. Unfortunately, this breaks down when UR functions are not part of the adapter interface but instead are implemented in the loader. There's no place for the layers to hook into.
This issue is to devise and implement a way for the proxy layers to intercept loader-only functions.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the loader, the proxy-layer adapters, and the adapter interface to identify loader-only functions and where layers currently intercept calls. Define how proxy layers should receive those functions, then verify that the affected loader operations can be intercepted without breaking existing adapter behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100