table of contents
CLGETGLCONTEXTINFOKH(3clc) | OpenCL Manual | CLGETGLCONTEXTINFOKH(3clc) |
NAME¶
clGetGLContextInfoKHR - Get OpenGL context information.
¶
cl_int clGetGLContextInfoKHR(const cl_context_properties *properties, cl_gl_context_info param_name, size_t param_value_size, void *param_value, size_t *param_value_size_ret);
PARAMETERS¶
properties
param_name
param_value_size
param_value
param_value_size_ret
param_name | Return Type | Information returned in param_value |
CL_CURRENT_DEVICE_FOR_GL_CONTEXT_KHR | cl_device_id | Return the CL device currently associated with the specified OpenGL context. |
CL_DEVICES_FOR_GL_CONTEXT_KHR | cl_device_id[] | List of all CL devices which may be associated with the specified OpenGL context. |
DESCRIPTION¶
The OpenGL object used to create the OpenCL memory object and information about the object type i.e. whether it is a texture, renderbuffer, or buffer object can be queried using this function.
NOTES¶
The OpenCL specification in section 9.7 defines how to share data with texture and buffer objects in a parallel OpenGL implementation, but does not define how the association between an OpenCL context and an OpenGL context or share group is established. This extension defines optional attributes to OpenCL context creation routines which associate a GL context or share group object with a newly created OpenCL context. If this extension is supported by an implementation, the string "cl_khr_gl_sharing" will be present in the CL_PLATFORM_EXTENSIONS or CL_DEVICE_EXTENSIONS string described in the table of allowed values for param_name for clGetDeviceInfo(3clc).
An OpenGL implementation supporting buffer objects and sharing of texture and buffer object images with OpenCL is required by this extension.
OpenCL device(s) corresponding to an OpenGL context may be queried. Such a device may not always exist (for example, if an OpenGL context is specified on a GPU not supporting OpenCL command queues, but which does support shared CL/GL objects), and if it does exist, may change over time. When such a device does exist, acquiring and releasing shared CL/GL objects may be faster on a command queue corresponding to this device than on command queues corresponding to other devices available to an OpenCL context.
ERRORS¶
Returns CL_SUCCESS if the function is executed successfully. If no device(s) exist corresponding to param_name, the call will not fail, but the value of param_value_size_ret will be zero. Otherwise returns one of the following:
and any of the following conditions hold:
SPECIFICATION¶
OpenCL Specification[1]
SEE ALSO¶
clCreateContext(3clc) cl_khr_gl_sharing(3clc)
AUTHORS¶
The Khronos Group
COPYRIGHT¶
Copyright © 2007-2011 The Khronos Group Inc.
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and/or associated documentation files (the
"Materials"), to deal in the Materials without restriction,
including without limitation the rights to use, copy, modify, merge,
publish, distribute, sublicense, and/or sell copies of the Materials, and to
permit persons to whom the Materials are furnished to do so, subject to the
condition that this copyright notice and permission notice shall be included
in all copies or substantial portions of the Materials.
NOTES¶
- 1.
- OpenCL Specification
01/14/2021 | The Khronos Group |