diff options
| author | Konsta Holtta <kholtta@nvidia.com> | 2017-03-30 03:17:01 -0400 |
|---|---|---|
| committer | mobile promotions <svcmobile_promotions@nvidia.com> | 2017-04-03 17:04:04 -0400 |
| commit | 2119213467a9e70a7e6cbf78d9b8954b27898716 (patch) | |
| tree | 23c01192a4839db00998353f1495b58e90c79e17 /drivers/gpu/nvgpu/gp10b/mc_gp10b.c | |
| parent | 7aa2f44e8b53dcd29ccb58a32f299819fca83bf6 (diff) | |
gpu: nvgpu: use NO_KERNEL_MAPPING for default vidmem
Commit 8f3875393e7a6bd0fc03afdb1fa99b7e33b71576 ("abstract away dma
alloc attrs") added an implicit NVGPU_DMA_NO_KERNEL_MAPPING for the
explicit vidmem buffer allocation path. The default allocation api that
chooses vidmem or sysmem based on available support still passed a zero
flag and produced a warning when the flag should have been there. Force
the NO_KERNEL_MAPPING flag on currently via the default-allocator api.
Commit 8a15e02ca92b83aa5a216ea9cd42680373212ecd ("gpu: nvgpu: add
NO_KERNEL_MAPPING for alloc_map_vid") did the same for flagless
alloc-and-map calls but this default alloc-only call got overlooked.
Also, store the flags in the mem_desc during allocation, just like in
the sysmem allocator, to be checked during freeing.
Bug 1896734
Bug 1853519
Change-Id: I4b4182b4fd52298bdd2a77197c095a23d2a67c4a
Signed-off-by: Konsta Holtta <kholtta@nvidia.com>
Reviewed-on: http://git-master/r/1331252
Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com>
Tested-by: mobile promotions <svcmobile_promotions@nvidia.com>
Diffstat (limited to 'drivers/gpu/nvgpu/gp10b/mc_gp10b.c')
0 files changed, 0 insertions, 0 deletions