Displaying 2 results from an estimated 2 matches for "gk20a_vm_map".
2015 Apr 16
2
[PATCH 6/6] mmu: gk20a: implement IOMMU mapping for big pages
...h"
> +
> +struct gk20a_mmu_priv {
> + struct nvkm_mmu base;
> +};
> +
> +struct gk20a_mmu_iommu_mapping {
> + struct nvkm_mm_node *node;
> + u64 iova;
> +};
> +
> +extern const u8 gf100_pte_storage_type_map[256];
> +
> +static void
> +gk20a_vm_map(struct nvkm_vma *vma, struct nvkm_gpuobj *pgt,
> + struct nvkm_mem *mem, u32 pte, u64 list)
> +{
> + u32 target = (vma->access & NV_MEM_ACCESS_NOSNOOP) ? 7 : 5;
> + u64 phys;
> +
> + pte <<= 3;
> + phys = gf100_vm_addr(vma, lis...
2015 Apr 16
15
[PATCH 0/6] map big page by platform IOMMU
Hi,
Generally the the imported buffers which has memory type TTM_PL_TT are
mapped as small pages probably due to lack of big page allocation. But the
platform device which also use memory type TTM_PL_TT, like GK20A, can
*allocate* big page though the IOMMU hardware inside the SoC. This is a try
to map the imported buffers as big pages in GMMU by the platform IOMMU. With
some preparation work to