From: Eric Anholt <eric@anholt.net>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Ensure that while(INREG()) are bounded.
Date: Fri, 06 Aug 2010 14:23:37 -0700 [thread overview]
Message-ID: <87lj8jmo4m.fsf@pollan.anholt.net> (raw)
In-Reply-To: <1281107514-3876-1-git-send-email-chris@chris-wilson.co.uk>
[-- Attachment #1.1: Type: text/plain, Size: 458 bytes --]
On Fri, 6 Aug 2010 16:11:54 +0100, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Add a new macro, wait_for, to simplify the act of waiting on a register
> to change state. wait_for() takes three arguments, the condition to
> inspect on every loop, the maximum amount of time to wait and whether to
> yield the cpu for a length of time after each check.
These failures seem DRM_ERROR()-worthy. What do you think? But I do
like the looks of this patch.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 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:[~2010-08-06 21:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 15:11 [PATCH] drm/i915: Ensure that while(INREG()) are bounded Chris Wilson
2010-08-06 21:23 ` Eric Anholt [this message]
2010-08-06 21:39 ` Chris Wilson
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=87lj8jmo4m.fsf@pollan.anholt.net \
--to=eric@anholt.net \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox