Revert "performance: enable staging write for cl buffers"

This reverts commit a9a2f7577f.

Signed-off-by: Szymon Morek <szymon.morek@intel.com>
This commit is contained in:
Szymon Morek
2025-01-24 15:30:40 +00:00
committed by Compute-Runtime-Automation
parent 9e4513914f
commit d7c8b42d01
2 changed files with 0 additions and 9 deletions

View File

@@ -173,7 +173,6 @@ bool CommandQueue::isValidForStagingTransfer(MemObj *memObj, const void *ptr, bo
switch (memObj->peekClMemObjType()) {
case CL_MEM_OBJECT_IMAGE1D:
case CL_MEM_OBJECT_IMAGE2D:
case CL_MEM_OBJECT_BUFFER:
return stagingBufferManager->isValidForStagingTransfer(this->getDevice(), ptr, hasDependencies);
default:
return false;

View File

@@ -730,12 +730,4 @@ HWTEST_F(WriteBufferStagingBufferTest, whenEnqueueStagingWriteBufferFailedThenPr
EXPECT_EQ(res, CL_INVALID_OPERATION);
EXPECT_EQ(1ul, mockCommandQueueHw.enqueueWriteBufferCounter);
}
HWTEST_F(WriteBufferStagingBufferTest, whenIsValidForStagingTransferCalledThenReturnCorrectValue) {
MockCommandQueueHw<FamilyType> mockCommandQueueHw(context.get(), device.get(), &props);
auto isStagingBuffersEnabled = device->getProductHelper().isStagingBuffersEnabled();
unsigned char ptr[16];
EXPECT_EQ(isStagingBuffersEnabled, mockCommandQueueHw.isValidForStagingTransfer(&buffer, ptr, false));
}