Searched refs:mappable (Results 1 – 18 of 18) sorted by relevance
93 if (!umem->mappable) in nvkm_umem_map()176 umem->mappable = true; in nvkm_umem_new()
12 bool mappable:1; member
96 args->v0.mappable = !!(type & NVKM_MEM_MAPPABLE); in nvkm_ummu_type()
31 __u8 mappable; member
27 to be more directly mappable to performance, by passing in a wanted data32 determines how much io bandwidth the process will get, it's directly mappable
23 output direct-mapped, MSI, non mappable regions. Each
106 if (args.mappable) mmu->type[i].type |= NVIF_MEM_MAPPABLE; in nvif_mmu_ctor()
24 range should be mappable as normal system memory would be
37 mappable frame buffer. It has been tested with tinyx (Xfbdev). It is known
1262 u32 mappable = device->func->resource_size(device, 1) >> PAGE_SHIFT; in nouveau_ttm_fault_reserve_notify() local1286 bo->mem.start + bo->mem.num_pages < mappable) in nouveau_ttm_fault_reserve_notify()1291 nvbo->placements[i].lpfn = mappable; in nouveau_ttm_fault_reserve_notify()1296 nvbo->busy_placements[i].lpfn = mappable; in nouveau_ttm_fault_reserve_notify()
20 mappable, while 'size' indicates how large a mapping region to
563 bool mappable, fenceable; in __i915_vma_set_map_and_fenceable() local571 mappable = vma->node.start + vma->fence_size <= i915_vm_to_ggtt(vma->vm)->mappable_end; in __i915_vma_set_map_and_fenceable()573 if (mappable && fenceable) in __i915_vma_set_map_and_fenceable()
105 of the DPRC, discover the hardware objects present (including mappable121 A DPRC has a mappable MMIO region (an MC portal) that can be used
84 to userspace for zero-copy writing. One mappable page (in terms of
186 There are a number of cases where a trigger might only be mappable to a
78 - memory-mappable data area for user-space applications for ease of
139 prompt "Maximum mappable memory available for flash IO"
2123 which is not mappable. In such a case, you have to transfer the data