From: Eric Anholt <eric@anholt.net>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Remove spurious warning "Failure to install fence"
Date: Sun, 18 Apr 2010 17:16:11 -0700 [thread overview]
Message-ID: <87bpdg2t6c.fsf@pollan.anholt.net> (raw)
In-Reply-To: <1270417973-6795-1-git-send-email-chris@chris-wilson.co.uk>
[-- Attachment #1.1: Type: text/plain, Size: 530 bytes --]
On Sun, 4 Apr 2010 22:52:53 +0100, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> This particular warning is harmless as we emit during the normal
> pinning process where the batch buffer requires more fences than is
> available without eviction. Only if we fail to evict enough fences does
> this become a problem, so include the requested number of fences in the
> ultimate *error* message.
>
> v2: Remember to compile test even trial patches to remove warnings.
Care to rebase (and test) this one against -next?
[-- 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
prev parent reply other threads:[~2010-04-19 0:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1270416921-25483-1-git-send-email-chris@chris-wilson.co.uk>
2010-04-12 17:10 ` [PATCH 1/3] drm/i915: Unbind the bo if the user requests a different alignment Eric Anholt
2010-04-12 17:23 ` Chris Wilson
2010-04-13 23:49 ` Eric Anholt
2010-04-14 9:29 ` Chris Wilson
2010-04-14 10:23 ` Daniel Vetter
2010-04-14 21:19 ` Eric Anholt
2010-04-19 4:07 ` Owain Ainsworth
[not found] ` <1270417973-6795-1-git-send-email-chris@chris-wilson.co.uk>
2010-04-19 0:16 ` Eric Anholt [this message]
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=87bpdg2t6c.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 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.