On 22/09/2017 21:12, Srivatsa, Anusha wrote:
Sending to intel-gfx.
-----Original Message-----
From: Ursulin, Tvrtko
Sent: Thursday, September 21, 2017 8:16 AM
To: Srivatsa, Anusha <anusha.srivatsa@xxxxxxxxx>; intel-
gfx@xxxxxxxxxxxxxxxxxxxx
Cc: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx>; Vetter, Daniel
<daniel.vetter@xxxxxxxxx>; Sundaresan, Sujaritha
<sujaritha.sundaresan@xxxxxxxxx>; Mateo Lozano, Oscar
<oscar.mateo@xxxxxxxxx>; Wajdeczko, Michal <Michal.Wajdeczko@xxxxxxxxx>
Subject: RE: [PATCH 1/2] drm/i915/guc: Add GuC Load time to dmesg log.
Hi,
For some reason this email hasn't appeared on the mailing list so apologies for a
lame Outlook reply.
Thanks Tvrtko. I corrected the address.
I thought we agreed to use a better time source than jiffies (ktime_get()) and also
that DRM_NOTE would get emitted only in the case of load time being over some
threshold. If it is in realm of normal it should be a normal DRM_DEBUG_DRIVER.
If it is over 20 ms (the threshold) wont DRM_ERROR be a better option? If it is within that limit, then the info will be in DRM_DEBUG_DRIVER from which the QA can pick it.
Error only if it fails to load I think. DRM_NOTE was for cases when it
succeeds but after taking unexpectedly long. Just so it is a level about
informational.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
