Re: [Nouveau] CUDA fixed VA allocations and sparse mappings

2015-07-13 Thread Andrew Chew
I apologize for my ignorance. In digging through nouveau, I've become a bit confused regarding the relationship between virtual address allocations and nouveau bo's. From my reading of the code, it seems that a nouveau_bo really encapsulates a buffer (whether imported, or allocated within

Re: [Nouveau] CUDA fixed VA allocations and sparse mappings

2015-07-07 Thread Andrew Chew
On Tue, Jul 07, 2015 at 11:29:38AM -0400, Ilia Mirkin wrote: On Mon, Jul 6, 2015 at 8:42 PM, Andrew Chew ac...@nvidia.com wrote: These ioctls just call into the allocator to allocate a range of addresses, resulting in a struct nvkm_vma that tracks that allocation (or releases the struct

Re: [Nouveau] CUDA fixed VA allocations and sparse mappings

2015-07-07 Thread Andrew Chew
On Wed, Jul 08, 2015 at 10:18:36AM +1000, Ben Skeggs wrote: There's some minimal state that needs to be mapped into GPU address space. One thing that comes to mind are pushbuffers, which are needed to submit stuff to any engine. I guess you can probably use the start of the kernel's address

Re: [Nouveau] CUDA fixed VA allocations and sparse mappings

2015-07-07 Thread Andrew Chew
On Wed, Jul 08, 2015 at 10:37:34AM +1000, Ben Skeggs wrote: On 8 July 2015 at 10:31, Andrew Chew ac...@nvidia.com wrote: On Wed, Jul 08, 2015 at 10:18:36AM +1000, Ben Skeggs wrote: There's some minimal state that needs to be mapped into GPU address space. One thing that comes to mind