Added chipset specific uuid retrieving functionality
This is used by zeDeviceGetProperties
Related-To: LOCI-2636
Signed-off-by: Joshua Santosh Ranjan <joshua.santosh.ranjan@intel.com>
Currently only supported scenario is one in order queue.
Instead of resolving dependencies via semaphores, do this with pipe controls.
Signed-off-by: Michal Mrozek <michal.mrozek@intel.com>
- add function for resolving builtins using relocations
- add relocation for __SubDeviceID symbol
Related-To: NEO-6258
Signed-off-by: Kamil Diedrich <kamil.diedrich@intel.com>
If a kernel has ray tracing calls, we allocate and initialize
per-device RTDispatchGlobals if needed, and hand off pointer to
the same into a running kernel via an implicit parameter.
Related-To: NEO-5384
Signed-off-by: Jim Snow <jim.m.snow@intel.com>
- update crossthreaddata size according to argument offsets
when processing patchtoken binary when DATA PARAMETER STREAM SIZE
is lower than size required for arguments
Signed-off-by: Mateusz Hoppe <mateusz.hoppe@intel.com>
Introduce the debug regkey OverrideMocsIndexForScratchSpace
to control MOCS index in surface state for scratch space
Related-To: NEO-6509
Signed-off-by: Milczarek, Slawomir <slawomir.milczarek@intel.com>
- Clear dependencies even if last engine changed
- Do no program semaphore waiting for blit when blit is submitted with gpgpu
- Track barrier timestamps to correctly synchronize blits in OOQ
Related-To: NEO-6444
Signed-off-by: Maciej Dziuban <maciej.dziuban@intel.com>
Fix problem with not enabled slices in mode SetCommandStreamReceiver=1
Related-To: NEO-6507
Signed-off-by: Katarzyna Cencelewska <katarzyna.cencelewska@intel.com>
Introduce the regkey OverrideL1CacheControlInSurfaceStateForScratchSpace
to control cache policy in surface state for scratch space
Related-To: NEO-3227
Signed-off-by: Milczarek, Slawomir <slawomir.milczarek@intel.com>
Simplify logic around engine groups.
Remove no longer needed code.
Ensure correct device is used when verifying engine groups.
Related-To: NEO-6219
Signed-off-by: Filip Hazubski <filip.hazubski@intel.com>
Multi tag allocation is useful only in openCL to ensure cross root
device synchronization based on tag address.
It is not required in level zero.
Futher multi tag allocation is causing instability in sysman
device reset. So, for level zero instead of multi tag allocation
create single tag allocation.
Related-To: LOCI-2651
Signed-off-by: Jitendra Sharma <jitendra.sharma@intel.com>
Signed-off-by: Kamil Kopryk <kamil.kopryk@intel.com>
Related-To: NEO-6075
After this change driver will fail clBuildProgram/zeModuleCreate api calls
whenever stateful access is discovered and device has shared system usm caps
enabled.This is required since in this case allocation greater than 4GB
will not work.
If user still wants to use stateful addressing mode,
-cl-opt-smaller-than-4GB-buffers-only / -ze-opt-smaller-than-4GB-buffers-only
build option should be passed as build option, but then user can not use
buffers greater than 4GB.
Crash on an attempt to read from tag address when ring is not started
Related-to: NEO-5869
Signed-off-by: Milczarek, Slawomir <slawomir.milczarek@intel.com>
