-
Notifications
You must be signed in to change notification settings - Fork 730
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[SYCL][XPTI] Refactoring framework to use 128-bit keys for collision …
…elimination (#14467) Previous implementation of the XPTI framework used 64-bit hash values to represent trace points in the code and this has led to a few of hash collisions.This refactoring moves to a 128-bit key to guarantee uniqueness. The changes needed to SYCL runtime to fully migrate to newer APIs will be pushed as a **separate Part 2 pull request**. Current pull request include changes to the XPTI framework and minor changes to SYCL runtime to reflect the transition to 128-bit keys and ensure validity of the tests. - 128-bit keys for internal storage and lookups - Support 64-bit universal IDs for backward compatibility - Updated tests to handle legacy API and new APIs for correctness tests - Updated performance tests to report metrics for both 64-bit and 28-bit native APIs - Updated SYCL instrumentation to return a new trace event for each instance of a trace point. Earlier implementation always returned the same trace event for a give trace point as the metadata associated with a trace event was deemed to be invariant. However, with the need for mutable metadata, this change is required. - Minor updates to documentation **NOTE**: Since more events are generated due to the creation of a new trace event for each trace point instance, some tests that rely on event sequences may have to be updated. --------- Signed-off-by: Vasanth Tovinkere <[email protected]> Signed-off-by: Tikhomirova, Kseniya <[email protected]> Co-authored-by: Tikhomirova, Kseniya <[email protected]> Co-authored-by: Artur Gainullin <[email protected]>
- Loading branch information
1 parent
f995f55
commit 283073a
Showing
28 changed files
with
6,375 additions
and
1,036 deletions.
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.