AI/rocm-systems
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

SWDEV-356567 - Remove notes for limitation of using start & end events of same hipExtLaunchKernelGGL in hipEventElapsedTime. (#3032)

Browse Source 
Change-Id: I6041f90f6e3a41d19697a31f31220aedfa5f2fa8
This commit is contained in:
ROCm CI Service Account
2022-10-27 20:24:17 +05:30
committed by GitHub
parent 5cc1262f21
commit 037cc162d0
2 changed files with 0 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
include/hip/hip_runtime_api.h
-7
View File
@@ -2477,13 +2477,6 @@ hipError_t hipEventSynchronize(hipEvent_t event);
* recorded on one or both events (that is, hipEventQuery() would return #hipErrorNotReady on at
* least one of the events), then #hipErrorNotReady is returned.
*
* Note, for HIP Events used in kernel dispatch using hipExtLaunchKernelGGL/hipExtLaunchKernel,
* events passed in hipExtLaunchKernelGGL/hipExtLaunchKernel are not explicitly recorded and should
* only be used to get elapsed time for that specific launch. In case events are used across
* multiple dispatches, for example, start and stop events from different hipExtLaunchKernelGGL/
* hipExtLaunchKernel calls, they will be treated as invalid unrecorded events, HIP will throw
* error "hipErrorInvalidHandle" from hipEventElapsedTime.
*
* @see hipEventCreate, hipEventCreateWithFlags, hipEventQuery, hipEventDestroy, hipEventRecord,
* hipEventSynchronize
*/