Closed maleadt closed 4 years ago
version
is correct. You don't need to set the other values, as that's the only input parameter, and the others are outputs (see definition for that struct here https://spec.oneapi.com/versions/0.6.0/oneL0/core/api.html?highlight=zedevicecanaccesspeer#ze-device-kernel-properties-t). The rest are set by the driver when retrieving the properties.
Reason that field retains the value is because it's a boolean, so the driver most likely is just setting up to true, which is the same as 100 :)
Reason that field retains the value is because it's a boolean, so the driver most likely is just setting up to true, which is the same as 100 :)
That doesn't appear to be the case, if I memset the struct to zero (or set the dp4aSupported field to 0) that value is preserved too, so it rather looks like the driver isn't setting anything.
Ok, so in this case, it looks like there's something missing in the implementation. Could you please create the issue in the Intel driver implementation, https://github.com/intel/compute-runtime, given that it looks like a bug in the GPU driver implementation and not in the loader?
Done!
This retains the
100
value. Am I supposed to zero-initialize these structs?Also, is the use of the
version
field correct here?