From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Andy Whitcroft <apw@canonical.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/4] drm/i915: Prevent fence-reuse stalls
Date: Sat, 19 Mar 2011 23:57:20 +0100 [thread overview]
Message-ID: <20110319225720.GE16343@viiv.ffwll.ch> (raw)
In-Reply-To: <1300487719-26578-5-git-send-email-chris@chris-wilson.co.uk>
On Fri, Mar 18, 2011 at 10:35:19PM +0000, Chris Wilson wrote:
> With the last bug preventing fence pipelining fixed (or at least the
> last known bug), re-enable pipelining to avoid stalling on fence
> acquisition between batches.
\o/ ... the cleaned-up get_fence code is definitely much less scary, so
I'm all for a new round lets-try-to-upset-gen3-gpus.
Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
prev parent reply other threads:[~2011-03-19 22:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 22:35 Pipelined fence fixes Chris Wilson
2011-03-18 22:35 ` [PATCH 1/4] drm/i915: Track fence setup separately from fenced object lifetime Chris Wilson
2011-03-19 22:35 ` Daniel Vetter
2011-03-19 22:42 ` Chris Wilson
2011-03-19 23:11 ` Daniel Vetter
2011-03-18 22:35 ` [PATCH 2/4] drm/i915: Invalidate fenced read domains upon flush Chris Wilson
2011-03-19 22:49 ` Daniel Vetter
2011-03-18 22:35 ` [PATCH 3/4] drm/i915: Cleanup handling of last_fenced_seqno Chris Wilson
2011-03-19 22:55 ` Daniel Vetter
2011-03-19 23:09 ` Chris Wilson
2011-03-18 22:35 ` [PATCH 4/4] drm/i915: Prevent fence-reuse stalls Chris Wilson
2011-03-19 22:57 ` Daniel Vetter [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=20110319225720.GE16343@viiv.ffwll.ch \
--to=daniel@ffwll.ch \
--cc=apw@canonical.com \
--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