From 2170c188288119979c11f98086241feb662879f8 Mon Sep 17 00:00:00 2001 From: Pratik Basyal Date: Tue, 18 Feb 2025 16:45:22 -0500 Subject: [PATCH] ROCTx marker known issue updated in 6.3.3. RN (#311) * ROCTx markers known issue updated * Leo's feedback incorporated --- RELEASE.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/RELEASE.md b/RELEASE.md index c1a268953..c4a620a66 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -406,6 +406,10 @@ The following sections describe key changes to ROCm components. ROCm known issues are noted on {fab}`github` [GitHub](https://github.com/ROCm/ROCm/labels/Verified%20Issue). For known issues related to individual components, review the [Detailed component changes](#detailed-component-changes). +### Zero value is displayed in ROCTx aggregated statistics + +The ROCTx markers are standalone markers within the ROCProfiler-SDK library. Each marker reports only a single timestamp, which is recorded as the `start_timestamp` and `end_timestamp`. As a result, the value for aggregated statistics presented in `TotalDurationNs`, `maxNs`, and `minNs`, is zero. The zero value indicates that the actual execution time is not associated with the markers, which is an expected behavior. + ## ROCm upcoming changes The following changes to the ROCm software stack are anticipated for future releases.