diff options
| author | Michel Dänzer <michel.daenzer@amd.com> | 2014-07-16 13:40:32 +0400 |
|---|---|---|
| committer | Alex Deucher <alexander.deucher@amd.com> | 2014-08-05 16:53:30 +0400 |
| commit | 380670aebfca998bb67b9cf05fc7f28ebeac4b18 (patch) | |
| tree | 64adb7bf11224ca06771adfc3465d07817ac40fb | |
| parent | 377bd8a98d7dccd9b71a1cef259821389f09da38 (diff) | |
| download | linux-380670aebfca998bb67b9cf05fc7f28ebeac4b18.tar.xz | |
drm/radeon: Demote 'BO allocation size too large' message to debug only
These clutter up dmesg during piglit runs. Userspace generally deals
gracefully with this failure.
Signed-off-by: Michel Dänzer <michel.daenzer@amd.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
| -rw-r--r-- | drivers/gpu/drm/radeon/radeon_gem.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/gpu/drm/radeon/radeon_gem.c b/drivers/gpu/drm/radeon/radeon_gem.c index d09650c1d720..fdd189b2b217 100644 --- a/drivers/gpu/drm/radeon/radeon_gem.c +++ b/drivers/gpu/drm/radeon/radeon_gem.c @@ -58,8 +58,8 @@ int radeon_gem_object_create(struct radeon_device *rdev, int size, /* maximun bo size is the minimun btw visible vram and gtt size */ max_size = min(rdev->mc.visible_vram_size, rdev->mc.gtt_size); if (size > max_size) { - printk(KERN_WARNING "%s:%d alloc size %dMb bigger than %ldMb limit\n", - __func__, __LINE__, size >> 20, max_size >> 20); + DRM_DEBUG("Allocation size %dMb bigger than %ldMb limit\n", + size >> 20, max_size >> 20); return -ENOMEM; } |