From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org, stable@kernel.org
Subject: Re: [PATCH] drm/i915: Mark untiled BLT commands as fenced on gen2/3
Date: Fri, 23 Mar 2012 20:03:23 +0100 [thread overview]
Message-ID: <20120323190323.GF4087@phenom.ffwll.local> (raw)
In-Reply-To: <1332326898-20080-1-git-send-email-chris@chris-wilson.co.uk>
On Wed, Mar 21, 2012 at 10:48:18AM +0000, Chris Wilson wrote:
> The BLT commands on gen2/3 utilize the fence registers and so we cannot
> modify any fences for the object whilst those commands are in flight.
> Currently we marked tiled commands as occupying a fence, but forgot to
> restrict the untiled commands from preventing a fence being assigned
> before they were completed.
>
> One side-effect is that we ten have to double check that a fence was
> allocated for a fenced buffer during move-to-active.
>
> Reported-by: Jiri Slaby <jirislaby@gmail.com>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=43427
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: stable@kernel.org
I've had a few comments on irc about a preliminary version of this patch,
and Chris addressed them all. So
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Futhermore I've stitched together a little testcase in i-g-t, and it
indeed blows up without this patch. So
Testcase: i-g-t/tests/gem_tiled_after_untiled_blt
Tested-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Cheers, Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2012-03-23 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 10:48 [PATCH] drm/i915: Mark untiled BLT commands as fenced on gen2/3 Chris Wilson
2012-03-23 19:03 ` Daniel Vetter [this message]
2012-03-28 11:20 ` Daniel Vetter
2012-03-23 20:49 ` 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=20120323190323.GF4087@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@kernel.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