Hi Andreas, Here is the pyopencl platform information:
> sudo DISPLAY=:0 python opencl-print-info.py PyOpenCL version: 2016.2.1 OpenCL header version: 1.2 - Installed platforms (SDKs) and available devices: NVIDIA CUDA (NVIDIA Corporation) Version: OpenCL 1.2 CUDA 8.0.0 Profile: FULL_PROFILE Extensions: ['cl_khr_global_int32_base_atomics', 'cl_khr_global_int32_extended_atomics', 'cl_khr_local_int32_base_atomics', 'cl_khr_local_int32_extended_atomics', 'cl_khr_fp64', 'cl_khr_byte_addressable_store', 'cl_khr_icd', 'cl_khr_gl_sharing', 'cl_nv_compiler_options', 'cl_nv_device_attribute_query', 'cl_nv_pragma_unroll', 'cl_nv_copy_opts', 'cl_khr_gl_event'] Available devices: Quadro K5000 (NVIDIA Corporation) Version: OpenCL 1.2 CUDA Type: GPU Extensions: ['cl_khr_global_int32_base_atomics', 'cl_khr_global_int32_extended_atomics', 'cl_khr_local_int32_base_atomics', 'cl_khr_local_int32_extended_atomics', 'cl_khr_fp64', 'cl_khr_byte_addressable_store', 'cl_khr_icd', 'cl_khr_gl_sharing', 'cl_nv_compiler_options', 'cl_nv_device_attribute_query', 'cl_nv_pragma_unroll', 'cl_nv_copy_opts', 'cl_khr_gl_event'] Memory (global): 4232183808 Memory (local): 49152 Address bits: 64 Max work item dims: 3 Max work group size: 1024 Max compute units: 8 Driver version: 375.51 Image support: True Little endian: True Device available: True Compiler available: True The following code displays 'NVIDIA CUDA' as the platform: print(cl.get_platforms()[0]) platform = cl.get_platforms()[0] context = cl.Context(properties=[(cl.context_properties.PLATFORM, platform)] + get_gl_sharing_context_properties()) queue = cl.CommandQueue(context) -- Aaron On Wed, Apr 12, 2017 at 2:08 PM, Andreas Kloeckner <li...@informa.tiker.net> wrote: > Aaron Myles Landwehr <a...@udel.edu> writes: > > I'm using NVs driver, the xorg log confirms this (as well as the glx > > extensions being loaded) and Opencl and Cuda also work outside of > pyopencls > > interop code (they require the NV driver to function). At this point, I'm > > thinking the pointer to the context is probably incorrect and that's > > probably why I'm seeing weird P and Rs printed as the display name since > > incorrect memory would likely be referenced in that case. > > Not sure how the 'wrong context' bit would happen--can you print > e.g. context.platform.name or something to ensure you're talking to the > right thing? > > Btw, please make sure the list stays cc'd. > > Andreas > >
_______________________________________________ PyOpenCL mailing list PyOpenCL@tiker.net https://lists.tiker.net/listinfo/pyopencl
