[NPU] Use different graph init

[pereanub]

Details:

• Use different graph init in case graph file schema or elf is used

Tickets:

• CVS-154233

[pereanub]

build_jenkins

[ArtemySkrebkov]

Interesting combination.

If I read it correctly, this semantic implies that we can change the pointer itself, but want to keep the data, pointer is pointing to, constant. Is it really required for this case?

[pereanub]

I changed this because it was also changed in the driver. And pfnGetNativeBinary2 requires a const pointer. Also, I think it make more sense these changes. We need to keep data(blob) as constant, indeed.

typedef ze_result_t (ZE_APICALL *ze_pfnGraphGetNativeBinary_ext_2_t)(
    ze_graph_handle_t hGraph,                       ///< [in] handle of the graph object
    size_t* pSize,                                  ///< [out] size of native binary in bytes
    const uint8_t** pGraphNativeBinary              ///< [out] double pointer to view of native binary, driver owns the mem
```ory
    );

[ArtemySkrebkov]

Is it possible to set both ZE_GRAPH_STAGE_INITIALIZE and ZE_GRAPH_STAGE_COMMAND_LIST_INITIALIZE?

If so, we can potentially call graph initialize twice.

[pereanub]

It shouldn't be possible right now. But we don't know what the future will be. We should check the bit and if it is set, just call it.

[ArtemySkrebkov]

If they are mutually exclusive, you can consider moving one of the if bodies into else if branch.

But it is more like a nitpick.

[pereanub]

yeah, I was thinking about this but we don't know for sure in the future how this change. Since that property is represented on bits makes more sense to check the bit instead of doing an if-else. In this way driver should decide if only one is needed, both, or none.

[ArtemySkrebkov]

Thanks for the explanations 👍

[ArtemySkrebkov]

If they are mutually exclusive, you can consider moving one of the if bodies into else if branch.

But it is more like a nitpick.