dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <deathsimple@vodafone.de>
To: "Michel Dänzer" <michel@daenzer.net>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/radeon: Demote 'BO allocation size too large' message to debug only
Date: Wed, 16 Jul 2014 11:41:50 +0200	[thread overview]
Message-ID: <53C648DE.7020908@vodafone.de> (raw)
In-Reply-To: <1405503632-2734-1-git-send-email-michel@daenzer.net>

Am 16.07.2014 11:40, schrieb Michel Dänzer:
> From: Michel Dänzer <michel.daenzer@amd.com>
>
> 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>

Already wanted to suggest the same thing,
Christian.

> ---
>   drivers/gpu/drm/radeon/radeon_gem.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/radeon/radeon_gem.c b/drivers/gpu/drm/radeon/radeon_gem.c
> index 07292aa..8584e43 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;
>   	}
>   

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2014-07-16  9:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16  9:40 [PATCH] drm/radeon: Demote 'BO allocation size too large' message to debug only Michel Dänzer
2014-07-16  9:41 ` Christian König [this message]
2014-07-16 16:12   ` Alex Deucher
2014-07-16 16:18     ` Christian König

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53C648DE.7020908@vodafone.de \
    --to=deathsimple@vodafone.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=michel@daenzer.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox