[Pkg-opencl-devel] Bug#769293: Bug#769293: beignet: upgrade or OCL_STRICT_CONFORMANCE change requires reboot

Giuseppe Bilotta giuseppe.bilotta at gmail.com
Wed Nov 12 18:30:04 UTC 2014


On Wed, Nov 12, 2014 at 5:30 PM, Rebecca N. Palmer
<rebecca_palmer at zoho.com> wrote:
>> Don't quite understand this issue. How do you set the
>> OCL_STRICT_CONFORMANCE?
>
> This is Debian's beignet 0.9.3~dfsg-1 (current unstable)
> and accuracy_speed_test.py from
> https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=19;filename=accuracy_speed_test.py;att=4;bug=768090
>
> rnpalmer at rnpalmer-laptop:~$ python3 ~/Debian/OpenCL/accuracy_speed_test.py
> [...]
> cos abs avg err: 1.72732e-05  max err: 6.10352e-05 rel avg err: 2.02569e-05
> max err: 6.10352e-05  time: 0.07409429550170898
> [...]
> rnpalmer at rnpalmer-laptop:~$ export OCL_STRICT_CONFORMANCE=1
> rnpalmer at rnpalmer-laptop:~$ python3 ~/Debian/OpenCL/accuracy_speed_test.py
> [...]
> cos abs avg err: 1.73168e-05  max err: 6.10352e-05 rel avg err: 2.03032e-05
> max err: 6.10352e-05  time: 0.0025167465209960938
> [...]

Could it be an issue with compiled kernel cache? I haven't looked at
how beignet handles this, but some platforms have some very aggressive
policy for compiled kernels. Can you try to find where beignet caches
its compiles and see if removing the cached kernels fixes this? If so,
the only thing that should be changed in beignet is that a kernel
cache invalidation on OCL_STRICT_CONFORMANCE change, or a way to have
separate caches for separate settings.


-- 
Giuseppe "Oblomov" Bilotta



More information about the Pkg-opencl-devel mailing list