fix: do not access UMD-managed SVM-allocation while in-use

[MaciejBielski]

It is illegal with UMD-managed migrations to access a SVM-allocation
from CPU side while it is still in-use on GPU side. In such scenario
a CPU-side access triggers data fetch from GPU-side and then any
subsequent GPU-side modification will not be observable on the CPU-side.
With UMD-managed migrations there is no way to tell the GPU that it
should fetch the allocation again from CPU-side before modifying it.

The removed EXPECT_NE statements are not mandatory for the goals of
the tests while their side-effects make things worse.

Signed-off-by: Maciej Bielski [email protected]

[MichalMrozek]

fix doesn't look correct, this access is fine if device supports concurrent access for shared usm between host & device which we turn on when we enable kmd migration.

Test needs to check for those caps and do not emit those memcpy if cap is not present

[HoppeMateusz]

the property is : ::ZE_MEMORY_CONCURRENT_ACCESS

zeDeviceGetMemoryAccessProperties(ze_device_handle_t hDevice, ze_device_memory_access_properties_t *pMemAccessProperties)

ze_memory_access_capabilities_t sharedSingleDeviceAllocCapabilities

if the test allocates shared USM.

i think SVM in commit message should be changed to USM.