<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - i915_init takes over 100 ms" href="https://bugs.freedesktop.org/show_bug.cgi?id=105622#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - i915_init takes over 100 ms" href="https://bugs.freedesktop.org/show_bug.cgi?id=105622">bug 105622</a> from <a class="email" href="mailto:pmenzel+bugs.freedesktop@molgen.mpg.de" title="Paul Menzel <pmenzel+bugs.freedesktop@molgen.mpg.de>"> Paul Menzel</a> <pre>Created <a href="attachment.cgi?id=138291" name="attach_138291" title="Screenshot from HTML output of `bootgraph.py`">attachment 138291</a> <a href="attachment.cgi?id=138291&action=edit" title="Screenshot from HTML output of `bootgraph.py`">[details]</a> Screenshot from HTML output of `bootgraph.py` (In reply to David Weinehall from <a href="show_bug.cgi?id=105622#c8">comment #8</a>) > From past experience I'd say that initcall_debug alone isn't a very useful > means to measure this. There's a tool called pm-graph that's great for > things like this. > > <a href="https://github.com/01org/pm-graph">https://github.com/01org/pm-graph</a> > > With that (in ftrace mode) I'm seeing roughly 35ms on the Broadwell I tested > on. I can test on KBL too, if you believe it'll make a difference (the BDW > was simply closest at hand). I know about pm-graph and the script `bootgraph.py` – you told me about the script (new name) `sleepgraph.py` in another report, if I remember correctly. ;-) Anyway, the times of initcall_debug and `bootgraph.py` match. This time I I measured it both show 50 ms, which is still quite a lot. > i915_init: start=4474.445, end=4525.887, length(w/o overhead)=50.175 ms, return=0 These 50 ms are spent in `generic_hdmi_init` of `snd_hda_codec_hdmi`.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>