Quoting David Weinehall (2017-11-01 13:38:48) > On Tue, Oct 31, 2017 at 05:11:20PM -0700, 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) > > > > v5: Rebased. Do not expose the load time variable in a global > > struct (Tvrtko, Joonas) > > From my point of view (measuring suspend/resume times) knowing > how much time is spent loading GuC & HuC is really useful, > so it's definitely useful information. This information could be gleaned from ftrace... -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
