Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Remove success dmesg noise for intel_rotate_pages()
Date: Wed, 22 Nov 2017 17:24:13 +0000	[thread overview]
Message-ID: <a5a21dee-ce14-79e1-490a-188fef84e9ed@linux.intel.com> (raw)
In-Reply-To: <151137076607.9619.6523085160364636669@mail.alporthouse.com>


On 22/11/2017 17:12, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2017-11-22 17:02:14)
>>
>> On 22/11/2017 14:56, Chris Wilson wrote:
>>> During selftesting intel_rotate_pages() is very, very verbose without
>>> giving us any information. Suppress the noise.
>>>
>>> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>>> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>> ---
>>>    drivers/gpu/drm/i915/i915_gem_gtt.c | 7 ++-----
>>>    1 file changed, 2 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/i915_gem_gtt.c b/drivers/gpu/drm/i915/i915_gem_gtt.c
>>> index e101b9a98957..41a203e0c160 100644
>>> --- a/drivers/gpu/drm/i915/i915_gem_gtt.c
>>> +++ b/drivers/gpu/drm/i915/i915_gem_gtt.c
>>> @@ -3737,9 +3737,6 @@ intel_rotate_pages(struct intel_rotation_info *rot_info,
>>>                                  rot_info->plane[i].stride, st, sg);
>>>        }
>>>    
>>> -     DRM_DEBUG_KMS("Created rotated page mapping for object size %zu (%ux%u tiles, %u pages)\n",
>>> -                   obj->base.size, rot_info->plane[0].width, rot_info->plane[0].height, size);
>>> -
>>
>> Fair.
>>
>>>        kvfree(page_addr_list);
>>>    
>>>        return st;
>>> @@ -3749,8 +3746,8 @@ intel_rotate_pages(struct intel_rotation_info *rot_info,
>>>    err_st_alloc:
>>>        kvfree(page_addr_list);
>>>    
>>> -     DRM_DEBUG_KMS("Failed to create rotated mapping for object size %zu! (%ux%u tiles, %u pages)\n",
>>> -                   obj->base.size, rot_info->plane[0].width, rot_info->plane[0].height, size);
>>> +     DRM_DEBUG_DRIVER("Failed to create rotated mapping for object size %zu! (%ux%u tiles, %u pages)\n",
>>> +                      obj->base.size, rot_info->plane[0].width, rot_info->plane[0].height, size);
>>
>> Keep the failure perhaps?
> 
> I did? We're not KMS here, we are the driver allocating a view.
> KMS/ATOMIC will get their turn to complain when they couldn't pin the
> vma. I have to admit I was tempted to remove it, but thought that was a
> step too far.

Joke is on me. :)

Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

Regards,

Tvrtko


_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-11-22 17:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-22 14:56 [PATCH] drm/i915: Remove success dmesg noise for intel_rotate_pages() Chris Wilson
2017-11-22 15:16 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-11-22 16:14 ` ✓ Fi.CI.IGT: " Patchwork
2017-11-22 17:02 ` [PATCH] " Tvrtko Ursulin
2017-11-22 17:12   ` Chris Wilson
2017-11-22 17:24     ` Tvrtko Ursulin [this message]
2017-11-22 18:38       ` Chris Wilson

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=a5a21dee-ce14-79e1-490a-188fef84e9ed@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    /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