From: Keith Packard <keithp@keithp.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/4] drm/i915: don't block resume on fb console resume v2
Date: Sat, 03 Nov 2012 09:33:20 -0700 [thread overview]
Message-ID: <86objek5nz.fsf@miki.keithp.com> (raw)
In-Reply-To: <1351880042-24935-1-git-send-email-jbarnes@virtuousgeek.org>
[-- Attachment #1.1: Type: text/plain, Size: 289 bytes --]
Jesse Barnes <jbarnes@virtuousgeek.org> writes:
> v2: use console_trylock() to try to resume the console immediately
> (Chris)
This will cause other printks to stall if i915 grabs the lock
first. Seems like a way to get random resume delays to me.
--
keith.packard@intel.com
[-- Attachment #1.2: Type: application/pgp-signature, Size: 827 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:[~2012-11-03 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 18:13 [PATCH 1/4] drm/i915: don't block resume on fb console resume v2 Jesse Barnes
2012-11-02 18:14 ` [PATCH 2/4] drm/i915: put ring frequency and turbo setup into a work queue v5 Jesse Barnes
2012-11-02 18:14 ` [PATCH 3/4] drm/i915: protect RPS/RC6 related accesses (including PCU) with a new mutex Jesse Barnes
2012-11-02 18:14 ` [PATCH 4/4] drm/i915: don't rewrite the GTT on resume v4 Jesse Barnes
2012-11-02 22:55 ` Daniel Vetter
2012-11-02 23:28 ` Jesse Barnes
2012-11-03 16:33 ` Keith Packard [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-02 16:39 [PATCH 1/4] drm/i915: don't block resume on fb console resume v2 Jesse Barnes
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=86objek5nz.fsf@miki.keithp.com \
--to=keithp@keithp.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.