From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Anusha Srivatsa <anusha.srivatsa@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Sujaritha Sundaresan <sujaritha.sundaresan@intel.com>
Subject: Re: [PATCH 1/2] drm/i915/guc: Add GuC Load time to dmesg log.
Date: Wed, 04 Oct 2017 15:51:48 +0300 [thread overview]
Message-ID: <1507121508.5856.5.camel@linux.intel.com> (raw)
In-Reply-To: <36bfb129-6cfa-22b0-bf08-fb525d49d28c@linux.intel.com>
On Wed, 2017-10-04 at 09:16 +0100, Tvrtko Ursulin wrote:
> On 04/10/2017 01:41, Anusha Srivatsa wrote:
> > Calculate the time that GuC takes to load using
> > jiffies. This information could be very useful in
> > determining if GuC is taking unreasonably long time
> > to load in a certain platforms.
> >
> > v2: Calculate time before logs are collected.
> > Move the guc_load_time variable as a part of
> > intel_uc_fw struct. Store only final result
> > which is to be exported to debugfs. (Michal)
> > Add the load time in the print message as well.
> >
> > v3: Remove debugfs entry. Remove local variable
> > guc_finish_load. (Daniel, Tvrtko)
> >
> > v4: Use ktime_get() instead of jiffies. Use DRM_NOTE
> > if time taken to load is more than the threshold. On
> > load times within acceptable range, use DRM_DEBUG_DRIVER
> > (Tvrtko)
> >
> > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Tvrtko ursulin <tvrtko.ursulin@intel.com>
> > Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> > Cc: Sujaritha Sundaresan <sujaritha.sundaresan@intel.com>
> > Cc: Oscar Mateo <oscar.mateo@intel.com>
> > Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> > Signed-off-by: Anusha Srivatsa <anusha.srivatsa@intel.com>
<SNIP>
> > @@ -373,6 +379,8 @@ int intel_guc_init_hw(struct intel_guc *guc)
> > guc->fw.path,
> > guc->fw.major_ver_found, guc->fw.minor_ver_found);
> >
> > + DRM_DEBUG_DRIVER("GuC is loaded in: %lld ms\n",guc->fw.load_time);
> > +
>
> If you move this debug to where the DRM_NOTE is you don't have to store
> the load time in the global structure. Unless there will be a reason in
> the future to have the value stored?
We decided not to expose it through debugfs, so let's try to avoid a
variable, too.
Regards, Joonas
PS. Also, lets try to get to the habit of having the S-o-b: and Cc:s in
chronological order. Less fixing for committers when applying patches.
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-10-04 12:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 0:41 [PATCH 1/2] drm/i915/guc: Add GuC Load time to dmesg log Anusha Srivatsa
2017-10-04 0:41 ` [PATCH 2/2] drm/i915/huc: Add HuC " Anusha Srivatsa
2017-10-04 1:05 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/guc: Add GuC " Patchwork
2017-10-04 3:02 ` ✓ Fi.CI.IGT: " Patchwork
2017-10-04 8:16 ` [PATCH 1/2] " Tvrtko Ursulin
2017-10-04 12:51 ` Joonas Lahtinen [this message]
2017-10-06 0:56 ` Srivatsa, Anusha
2017-10-06 6:29 ` Joonas Lahtinen
2017-10-09 17:24 ` Srivatsa, Anusha
2017-10-06 0:41 ` Srivatsa, Anusha
-- strict thread matches above, loose matches on Subject: below --
2017-11-01 0:11 Anusha Srivatsa
2017-11-01 13:14 ` Michal Wajdeczko
2017-11-01 13:24 ` Chris Wilson
2017-11-02 20:28 ` Anusha Srivatsa
2017-11-02 20:33 ` Chris Wilson
2017-11-02 18:04 ` Anusha Srivatsa
2017-11-01 13:38 ` David Weinehall
2017-11-01 13:48 ` Chris Wilson
[not found] <1505954668-2748-1-git-send-email-anusha.srivatsa@intel.com>
[not found] ` <9108028B3EB68E4CA5158371AB76E601633C4616@IRSMSX106.ger.corp.intel.com>
2017-09-22 20:12 ` Srivatsa, Anusha
2017-09-25 8:31 ` Tvrtko Ursulin
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=1507121508.5856.5.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=anusha.srivatsa@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=sujaritha.sundaresan@intel.com \
--cc=tvrtko.ursulin@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox