On 30/06/17 08:22 PM, Christian König wrote: > From: Christian König <[email protected]> > > We can finally remove this now. > > Signed-off-by: Christian König <[email protected]> > --- > drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c | 11 ----------- > 1 file changed, 11 deletions(-) > > diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c > b/drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c > index 96c4493..2382785 100644 > --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c > +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c > @@ -58,17 +58,6 @@ int amdgpu_gem_object_create(struct amdgpu_device *adev, > unsigned long size, > alignment = PAGE_SIZE; > } > > - if (!(initial_domain & (AMDGPU_GEM_DOMAIN_GDS | AMDGPU_GEM_DOMAIN_GWS | > AMDGPU_GEM_DOMAIN_OA))) { > - /* Maximum bo size is the unpinned gtt size since we use the > gtt to > - * handle vram to system pool migrations. > - */ > - max_size = adev->mc.gtt_size - adev->gart_pin_size; > - if (size > max_size) { > - DRM_DEBUG("Allocation size %ldMb bigger than %ldMb > limit\n", > - size >> 20, max_size >> 20); > - return -ENOMEM; > - } > - }
Do we still need to limit the size of VRAM BOs? If not, remove the now unused max_size local. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer _______________________________________________ amd-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/amd-gfx
