[Question] Measuring page-faults
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- performance, tooling
Research direction
Start with the Level Zero Tools API page linked in the issue and the zet_debug_event_info_page_fault_t structure it names. Determine whether the repository documents or exposes a query path for page-fault events associated with a Level-Zero buffer. Done should be a confirmed usage example or a clear statement of the supported API path.
Written by the indexing model from the issue text.
Description
Is there any example of how to measure page-faults associated with a Level-Zero buffer with Level Zero?
I guess I would need this data structure: zet_debug_event_info_page_fault_t but I can't find how to query this.
https://spec.oneapi.io/level-zero/latest/tools/api.html#zet-debug-event-info-page-fault-t
I am looking for something similar to NVIDIA nvprof and "GPU page fault groups" but for Intel GPUs with Level Zero.
- Dominant language
- C++
- Stars
- 335
- Forks
- 140
- Avg merge
- 12h 32m
- Merged PRs (30d)
- 5
Contributor guide
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.
More from oneapi-src/level-zero
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
oneapi-src/level-zero#495 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oneapi-src/level-zero#485 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
oneapi-src/level-zero#447 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
oneapi-src/level-zero#482 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
oneapi-src/level-zero#419 ·
All issues in oneapi-src/level-zero
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
duckdb/duckdb-wasm#2258 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
objectionary/eo-graphs#75 ·
-
Coarray integration tests carry no LABELS, so run_tests.py silently skips them under every backend Opencoarray
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FISCO-BCOS/FISCO-BCOS#5642 ·