Virtualbox and

OpenCL application on Fedora 20 on host machine works, and strace says that it loads On vmachine inside Virtualbox the program fails at clCreateContext; strace says it doesn't find

/proc/cpuinfo at host machine says that model name is Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz, stepping is 9 and cpuid level is 13. On virtual machine cpuid level is 5. Is this related?

Is there some deep problem with OpenCL and virtualization? If not, known problem  with Virtualbox?


Coupling of OpenCL runtime versions between CPU and GPU drivers

I am trying to compare OpenCL kernel performance on some different CPUs, and I would like to use the same device version for this. For the machines that don't have an Intel GPU, I am using the CPU only runtime (, which makes the CPU Device report "OpenCL 1.2 (Build 80752)" as the version. That's all fine and good. But one of my machines is an i7-4700EQ with 4600 Graphics. I understand that for this machine, the CPU device support is also provided through the Graphics driver.

Java 多线程编程(生产者和消费者问题以及死锁)

对于多线程程序来说,不管任何编程语言,生产者和消费者模型都是最经典的。就像学习每一门编程语言一样,Hello World!都是最经典的例子。
* Java线程:并发协作-生产者消费者模型 

Android 开发环境搭建教程



在开始Android开发之旅启动之前,首先要搭建环境 。打包下载开发环境所需软件




Announcing new Beta version of the Intel® SDK for OpenCL™ Applications 2014

Dear OpenCL developers,

I’m happy to announce the availability of the 2014 Beta version of the OpenCL SDK. Sign up and download now here.

The Intel® SDK for OpenCL™ Applications 2014 Beta extends the already supported Windows* operating systems with the Android*OS support. Comparing to the Intel® SDK for OpenCL™ Applications 2013 version, this new 2014 Beta software brings the following new features and capabilities:

Barrier error, when using __local qualified memory


"aftrer using barrier function the value in memory, which is qualified as __local, is changed."



I could narrow down the range.

The problem comes from using barrier when I read and write some data in memory(array), which is qualified as __local.

I didn't see there is some limitation  the memory area must be used as only reading or writing.

But it seems to be operated that there is the cache and when local memory is read, that is saved in cache and flush when I use barrier, which argument is  "CLK_LOCAL_MEM_FENCE"

Subscribe to Partners