intel/compute-runtime
1
0
Fork 0
mirror of https://github.com/intel/compute-runtime.git synced 2025-12-21 17:29:14 +08:00
Code Issues Packages Projects Releases Wiki Activity

documentation: update documentation about WaitOnMem

Browse Source 
Related-To: GSD-6482

Remove "Known Issues and Limitations" section
from documentation of wait and write on memory

Signed-off-by: Lu, Wenbin <wenbin.lu@intel.com>
This commit is contained in:
Lu, Wenbin
2023-10-20 05:45:45 +00:00
committed by Compute-Runtime-Automation
parent 0c960322f7
commit 5c162e2bd7
1 changed files with 1 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
level_zero/doc/experimental_extensions/WAIT_AND_WRITE_ON_MEMORY.md
View File

@@ -1,6 +1,6 @@
<!--- <!---
Copyright (C) 2022 Intel Corporation Copyright (C) 2022-2023 Intel Corporation
SPDX-License-Identifier: MIT SPDX-License-Identifier: MIT
@@ -10,7 +10,6 @@ SPDX-License-Identifier: MIT
* [Overview](#Overview) * [Overview](#Overview)
* [Definitions](#Definitions) * [Definitions](#Definitions)
* [Known Issues and Limitations](#Known-Issues-and-Limitations)
# Overview # Overview
@@ -101,8 +100,3 @@ zex_write_to_mem_desc_t writeDesc = {};
uint32_t signalData = 0x2; uint32_t signalData = 0x2;
pfnWriteMemFn(cmdList, &writeDesc, zeBuffer, signalData); pfnWriteMemFn(cmdList, &writeDesc, zeBuffer, signalData);
``` ```
# Known Issues and Limitations
- Hangs may be seen when using BCS for appending memory copy with IPC buffers and if waitOnMemory is performed on any queue (CCS or BCS).
- Workaround is to use a barrier after WaitOnMemory and before any subsequent action.