Received from Lev Givon on Mon, Jun 28, 2010 at 10:45:33PM EDT:
> Received from Louis Theran on Thu, Jun 24, 2010 at 12:22:19PM EDT:
> > On Wed, Jun 23, 2010 at 11:56 PM, Andreas Kloeckner <li...@informa.tiker.net
> > > wrote:
> >
> > >
> > > There's only *the* current runtime context for the current
> > > thread. "Specified" makes no sense--there isn't even a data type for
> > > it in the runtime. (also see previous email)
> > >
> >
> >
> > If these context stack operations are totally blind, which I didn't
> > understand, then I don't really understand the comment from the other email:
> >
> > To get garbage collection right in the face of multiple contexts, PyCUDA
> > > must assume there *is* a context and try to restore it at destruction time
> > > of every object created.
> >
> >
> > What's the heuristic being used? I was under the impression that there was
> > a CUContext type in the driver API.
> >
> > I will try to put together a patch along the lines you describe, although
> > the exact design pattern for mixing kernel code and runtime code seems to
> > not be fully worked out .
>
> After updating to the just-released (basic version of) CULA 2.0 and
> CUDA 3.1, I was able to successfully run a PyCUDA program [1] that
> calls CULA device functions using an unmodified installation of PyCUDA
> 0.94rc. Can anyone confirm this?
>
> L.G.
>
> [1] http://pastebin.com/n1yFsLR3
It also works with CUDA 3.0.
L.G.
_______________________________________________
PyCUDA mailing list
PyCUDA@tiker.net
http://lists.tiker.net/listinfo/pycuda
