Engine - Extensions#

oneAPI Level Zero Specification - Version 1.18.31

Engine - Extension Functions#

zesEngineGetActivityExt#

Added in version 1.7

ZE_APIEXPORT ze_result_t ZE_APICALL zesEngineGetActivityExt(zes_engine_handle_t hEngine, uint32_t *pCount, zes_engine_stats_t *pStats)#

Get activity stats for Physical Function (PF) and each Virtual Function (VF) associated with engine group.

  • The application may call this function from simultaneous threads.

  • The implementation of this function should be lock-free.

Parameters:
  • hEngine – [in] Handle for the component.

  • pCount – [in,out] Pointer to the number of VF engine stats descriptors.

    • if count is zero, the driver shall update the value with the total number of engine stats available.

    • if count is greater than the total number of engine stats available, the driver shall update the value with the correct number of engine stats available.

    • The count returned is the sum of number of VF instances currently available and the PF instance.

  • pStats – [in,out][optional][range(0, *pCount)] array of engine group activity counters.

    • if count is less than the total number of engine stats available, then driver shall only retrieve that number of stats.

    • the implementation shall populate the vector with engine stat for PF at index 0 of the vector followed by user provided pCount-1 number of VF engine stats.

Returns:

Engine - Extension Structures#

zes_engine_ext_properties_t#

Added in version 1.7

struct zes_engine_ext_properties_t#

Extension properties related to Engine Groups.

Public Members

zes_structure_type_t stype#

[in] type of this structure

void *pNext#

[in,out][optional] must be null or a pointer to an extension-specific structure (i.e. contains stype and pNext).

uint32_t countOfVirtualFunctionInstance#

[out] Number of Virtual Function(VF) instances associated with engine to monitor the utilization of hardware across all Virtual Function from a Physical Function (PF) instance. These VF-by-VF views should provide engine group and individual engine level granularity. This count represents the number of VF instances that are actively using the resource represented by the engine handle.