Displaying 2 results from an estimated 2 matches for "nouveau_gem_new_fix".
Did you mean:
nouveau_gem_new_fixed
2015 Jul 07
5
CUDA fixed VA allocations and sparse mappings
Hello,
I am currently looking into ways to support fixed virtual address allocations
and sparse mappings in nouveau, as a step towards supporting CUDA.
CUDA requires that the GPU virtual address for a given buffer match the
CPU virtual address. Therefore, when mapping a CUDA buffer, we have to have
a way of specifying a particular virtual address to map to (we would ask that
the CPU virtual
2015 Jul 07
2
CUDA fixed VA allocations and sparse mappings
..., etc. (and/or move between VRAM and GART
> and system/swap). I suspect that your target here are the GK20A and
> GM20B chips which don't have dedicated VRAM, but the ioctl's need to
> work for everything.
>
> Would it be sufficient to extend NOUVEAU_GEM_NEW or create a
> NOUVEAU_GEM_NEW_FIXED or something? IOW, why do have to separate the
> concept of a GEM object and a VM allocation?
Well maybe something like i did for radeon. With radeon you have 2 set of
ioctl. One to create/delete bo (GEM stuff) and one to associate a virtual
address with a bo. I wanted to let the userspace de...