dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <deathsimple@vodafone.de>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: "Michel Dänzer" <michel@daenzer.net>,
	"Maling list - DRI developers" <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 18:18:47 +0200	[thread overview]
Message-ID: <53C6A5E7.6030805@vodafone.de> (raw)
In-Reply-To: <CADnq5_MvsyWifoYFaUq9MRr6vTQ3GWrfpMi7+sno=8Shw3S6vg@mail.gmail.com>

Am 16.07.2014 18:12, schrieb Alex Deucher:
> On Wed, Jul 16, 2014 at 5:41 AM, Christian König
> <deathsimple@vodafone.de> wrote:
>> 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,
> Applied to my 3.17 tree.  Is there any reason we can't remove or relax
> this limit check in general?  At the very least I think we can remove
> the visible vram limit.

Already thought about that as well. Since we fixed the fallback to GTT 
if a buffer won't fit into VRAM on CPU access I offhand don't see any 
obstacle to relaxing this test.

We should just test if that fallback can handle to larges buffers 
gracefully.

Christian.

>
> Alex
>
>> 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

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

      reply	other threads:[~2014-07-16 16:19 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
2014-07-16 16:12   ` Alex Deucher
2014-07-16 16:18     ` Christian König [this message]

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=53C6A5E7.6030805@vodafone.de \
    --to=deathsimple@vodafone.de \
    --cc=alexdeucher@gmail.com \
    --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