I would like to be able to detect and access the Intel GPUs using OpenCL even over RDP/Remote Desktop sessions so that I can deploy applications that can utilize the full system capabilities even without direct console access. Right now, it appears that I would have to switch to use an alternate remote access client like VNC to keep the Intel video drivers loaded and keep the GPU accessible.
When I pass an array of 2 wait events into clEnqueueReadBuffer, with one event created manually, the ref counts are not incremented.
As I understand, all events passed into cl methods should get their ref counts incremented.
This works correctly with my GPU, but not for CPU (WIndows 7 64 bit, core i7 3770, latest Intel OpenCL driver for CPU)
My posts are all spam filtered - unable to post.
I suspect there's an aspect of clSetEventCallback that I'm misunderstanding. If you have a look at this simplified code below, you can see a kernel call, followed by a clSetEventCallback. The program then sits and waits on a windows event (inside the callback) to be set.
If the clSetEventCallback is immediately followed by a clFlush(), then the callback is called and the wait released as expected. However without the clFlush, the kernel is never called, nor its callback, and the wait is eternal. What am I missing here?
I want to develop openCl code that will work on Intel Iris Pro 6200 or 6300. I want to know the tools that support openCl for this device.
I am using Visual Studio Community 2013 Version 12 Update 4 and OpenCL Code Builder 18.104.22.168 on 64-bit laptop (Windows 8.1, Intel Core i5-5200U and GPU HD Graphics 5500).
When I try to run occupancy for kernels, I get a script error. On line 2863, character 98, ":" was expected.
How can I fix the problem?
Thanks in advance