From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Scott James Remnant <keybuk@google.com>
Cc: intel-gfx@lists.freedesktop.org,
"Stéphane Marchesin" <marcheu@google.com>,
"Daniel Stone" <daniels@collabora.com>
Subject: Re: i915_init takes a full second of kernel init time
Date: Tue, 13 Dec 2011 12:02:52 -0800 [thread overview]
Message-ID: <20111213120252.07f4c1a3@jbarnes-desktop> (raw)
In-Reply-To: <CAHZ1yCmNP9p3pZYidBoag9dTgpRfZDCJZJBU5R62ZE21WtZijA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 665 bytes --]
On Tue, 13 Dec 2011 11:55:06 -0800
Scott James Remnant <keybuk@google.com> wrote:
> I've been investigating Chrome OS boot time and noticed the anomaly
> where i915_init takes up a considerable amount of kernel startup time,
> one second in fact. I've attached a full dmesg with drm.debug=0xff for
> analysis at Daniel's suggestion.
I'm not surprised... we haven't optimized init time in awhile and lots
of delays have crept in.
What kind of panel does this laptop have? Can you enable drm debugging
(drm.debug=1 on the boot line) and see where the big delays are in
modesetting?
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2011-12-13 20:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 19:55 i915_init takes a full second of kernel init time Scott James Remnant
2011-12-13 20:02 ` Jesse Barnes [this message]
2011-12-13 21:34 ` Scott James Remnant
2011-12-13 22:01 ` Jesse Barnes
2011-12-13 22:21 ` Chris Wilson
2011-12-15 0:38 ` Scott James Remnant
2011-12-15 10:38 ` Chris Wilson
2011-12-15 17:48 ` Keith Packard
2011-12-15 21:48 ` Scott James Remnant
2011-12-15 22:22 ` Keith Packard
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=20111213120252.07f4c1a3@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=daniels@collabora.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=keybuk@google.com \
--cc=marcheu@google.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