From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: "Konduru, Chandra" <chandra.konduru@intel.com>
Cc: "Intel-gfx@lists.freedesktop.org" <Intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/skl: Bypass debug message if scalers are not requested
Date: Wed, 05 Aug 2015 16:02:38 +0100 [thread overview]
Message-ID: <55C2258E.3060607@linux.intel.com> (raw)
In-Reply-To: <55C21B7F.4050900@linux.intel.com>
On 08/05/2015 03:19 PM, Tvrtko Ursulin wrote:
[snip]
>>>>> Atomic is really complicated, but doing fully diagnostics for each
>>>>> frame
>>>>> is also way too noisy. For that reason we've add a DRM_DEBUG_ATOMIC
>>>>> which
>>>>> can be used for all these state tracking debug lines.
>>>>
>>>> We didn't do anything here and I just noticed kernel is still too
>>>> spammy
>>>> with regards to this issue.
>>>>
>>>> Should we just merge my patch? Still looks completely safe to me...
>>>
>>> doesn't seem to apply any more:(
>>
>> Yeah only some months have passed, who would have thought. :)
>>
>> But I realized that would be only one of the three log lines per cursor
>> update - there is a code path calling skl_detach_scaler two times as
>> well. Looks like this overall, per update:
>>
>> [drm:intel_atomic_setup_scalers] crtc_state = ffff880074b55c00 need = 0
>> avail = 2 scaler_users = 0x0
>> [drm:skl_detach_scaler] CRTC:21 Disabled scaler id 0.0
>> [drm:skl_detach_scaler] CRTC:21 Disabled scaler id 0.1
>>
>> I'll rebase this patch for a start.
>
> Sent it as a new thread but forgot v2 in the subject.
>
> Other source of spam is probably intel_begin_crtc_commit ->
> skl_detach_scalers.
>
> Don't know what the right fix would be there. Looks like it is not
> tracking transitions in scaler use so it would be able to act and log
> when something interesting happens, but rather does it every time. I
> defer to Chandra. :)
Ok I've sent something named "[PATCH] drm/i915/skl: Only disable scalers
once".
It was only compile tested due my current lack of suitable hardware for
testing. And I don't pretend to be confident in the world of atomic
states etc. so it may well be completely wrong.
So either scrutinize it a lot please, or let it be a motivator to come
up with a proper fix of your own. :)
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-08-05 15:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 16:08 [PATCH] drm/i915/skl: Bypass debug message if scalers are not requested Tvrtko Ursulin
2015-04-24 16:30 ` Konduru, Chandra
2015-04-24 16:33 ` Tvrtko Ursulin
2015-04-24 17:52 ` Konduru, Chandra
2015-04-24 18:07 ` Konduru, Chandra
2015-05-04 14:29 ` Daniel Vetter
2015-08-05 13:20 ` Tvrtko Ursulin
2015-08-05 13:58 ` Daniel Vetter
2015-08-05 14:12 ` Tvrtko Ursulin
2015-08-05 14:19 ` Tvrtko Ursulin
2015-08-05 15:02 ` Tvrtko Ursulin [this message]
2015-04-28 8:24 ` shuang.he
-- strict thread matches above, loose matches on Subject: below --
2015-08-05 14:14 Tvrtko Ursulin
2015-08-12 5:49 ` shuang.he
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=55C2258E.3060607@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=chandra.konduru@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.