- product helper sets flag in GfxCoreHelper - this allows to control
secondary contexts support per product - not whole core family
Related-To: NEO-13789
Signed-off-by: Mateusz Hoppe <mateusz.hoppe@intel.com>
Motivation is to distinguish between host USM resources and internal
driver resources allocated in host memory.
Related-To: NEO-13847
Signed-off-by: Lukasz Jobczyk <lukasz.jobczyk@intel.com>
mechanism for freeing allocations saved for reuse that have not been
used in a given time
Related-To: NEO-13425
Signed-off-by: Dominik Dabek <dominik.dabek@intel.com>
When on DC flush platform do not signal in order allocation when using
timestamp CB event. Handle wait on that event and synchronization using
in order timestamp node. Flush DC from wait. In order handled by pipe
controls.
Related-To: NEO-13441
Signed-off-by: Lukasz Jobczyk <lukasz.jobczyk@intel.com>
Create shared allocations to maintain reference timestamps.
Add flag to IPC pool data to check whether mapped time stamp
flag is set.
Related-To: NEO-12313
Signed-off-by: Bellekallu Rajkiran <bellekallu.rajkiran@intel.com>
Create shared allocations to maintain reference timestamps.
Add flag to IPC pool data to check whether mapped time stamp
flag is set.
Related-To: NEO-12313
Signed-off-by: Bellekallu Rajkiran <bellekallu.rajkiran@intel.com>
- reserve exact number of slots for scratch surface states in surface
state heaps
- do not use offsets for contexts depending on engine type executing
cmdlists
Signed-off-by: Mateusz Hoppe <mateusz.hoppe@intel.com>
The `initDriver` function had an issue where a new `result` variable was defined
in a lower scope, causing the initialization result to be discarded. This commit
removes the redundant variable declaration, ensuring that the `result` variable
initialized in the upper scope is correctly set by the
`Driver::get()->initialize` method and properly reflects the driver
initialization status.
Related-To: NEO-13686
Signed-off-by: Jack Myers <jack.myers@intel.com>
When on DC flush platform do not signal in order allocation when using
timestamp CB event. Handle wait on that event and synchronization using
in order timestamp node. Flush DC from wait. In order handled by pipe
controls.
Related-To: NEO-13441
Signed-off-by: Lukasz Jobczyk <lukasz.jobczyk@intel.com>
When on DC flush platform resolve in order implicit dependency with pipe
control.
Related-To: NEO-13441
Signed-off-by: Lukasz Jobczyk <lukasz.jobczyk@intel.com>
When on DC flush platform resolve in order implicit dependency with pipe
control.
Related-To: NEO-13441
Signed-off-by: Lukasz Jobczyk <lukasz.jobczyk@intel.com>
Addresses regressions from the reverted merge
of the tbx fault manager for host memory.
Recursive locking of mutex caused deadlock.
To fix, separate tbx fault data from base
cpu fault data, allowing separate mutexes
for each, eliminating recursive locks on
the same mutex.
By separating, we also help ensure that tbx-related
changes don't affect the original cpu fault manager code
paths.
As an added safe guard preventing critical regressions
and avoiding another auto-revert, the tbx fault manager
is hidden behind a new debug flag which is disabled by default.
Related-To: NEO-12268
Signed-off-by: Jack Myers <jack.myers@intel.com>
- Temporarily disables Multi-Threaded ULTs, to be
re-enabled in a separate dedicated test binary
Related-To: NEO-11488
Signed-off-by: Raiyan Latif <raiyan.latif@intel.com>
