oneapi-src / oneapi-src/unified-runtime
Track handle hierarchy in the validation layer
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 57
- Forks
- 120
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 1
Description
Validation layer currently does not differentiate between different types of handles. Its all just pointers. However, there's sufficient information to track both the type of a handle and the hierarchy of handles in a UR-based application (e.g., devices belong to a platform). Implementing such tracking would allow the validation layer to tell whether correct handles are used in a call (e.g., correct pair of context and device) and whether resources are released in the correct order (i.e., all platforms belonging to an adapter are released before the adapter itself is released).
- Handle correctness and compatibility checks.
- Release order checks.
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
The issue identifies the validation layer and UR-based applications but names no files, tests, or entry points. Begin by locating the validation-layer implementation and its handle representation. Done means the issue’s handle compatibility and release-order checks are implemented and both checklist items can be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100