From: Daniel Vetter <daniel@ffwll.ch>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/i915: FBC flush nuke for BDW
Date: Mon, 4 Aug 2014 10:11:47 +0200 [thread overview]
Message-ID: <20140804081147.GL8727@phenom.ffwll.local> (raw)
In-Reply-To: <20140801140729.GB4193@intel.com>
On Fri, Aug 01, 2014 at 05:07:30PM +0300, Ville Syrjälä wrote:
> On Thu, Jul 31, 2014 at 12:07:44PM -0700, Rodrigo Vivi wrote:
> > According to spec FBC on BDW and HSW are identical without any gaps.
> > So let's copy the nuke and let FBC really start compressing stuff.
> >
> > Without this patch we can verify with false color that nothing is being
> > compressed. With the nuke in place and false color it is possible
> > to see false color debugs.
> >
> > v2: Fix rebase conflict.
> >
> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_ringbuffer.c | 12 ++++++++++--
> > 1 file changed, 10 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > index 2908896..4ba3db1 100644
> > --- a/drivers/gpu/drm/i915/intel_ringbuffer.c
> > +++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > @@ -406,6 +406,7 @@ gen8_render_ring_flush(struct intel_engine_cs *ring,
> > {
> > u32 flags = 0;
> > u32 scratch_addr = ring->scratch.gtt_offset + 2 * CACHELINE_BYTES;
> > + int ret;
> >
> > flags |= PIPE_CONTROL_CS_STALL;
> >
> > @@ -424,7 +425,14 @@ gen8_render_ring_flush(struct intel_engine_cs *ring,
> > flags |= PIPE_CONTROL_GLOBAL_GTT_IVB;
> > }
> >
> > - return gen8_emit_pipe_control(ring, flags, scratch_addr);
> > + ret = gen8_emit_pipe_control(ring, flags, scratch_addr);
> > + if (ret)
> > + return ret;
> > +
> > + if (!invalidate_domains && flush_domains)
> > + return gen7_ring_fbc_flush(ring, FBC_REND_NUKE);
> > +
> > + return 0;
> > }
> >
> > static void ring_write_tail(struct intel_engine_cs *ring,
> > @@ -2065,7 +2073,7 @@ static int gen6_ring_flush(struct intel_engine_cs *ring,
> > }
> > intel_ring_advance(ring);
> >
> > - if (IS_GEN7(dev) && !invalidate && flush)
> > + if (INTEL_INFO(dev)->gen >= 7 && !invalidate && flush)
> > return gen7_ring_fbc_flush(ring, FBC_REND_CACHE_CLEAN);
>
> Apparently BDW has problems with LRIs to certain register offsets on
> !RCS and this here would hit that. The suggested workaround is to emit
> such LRIs only from RCS. Doing that would also involve tossing in a
> semaphore, so it feels like something that ought to be handled
> somewhere a bit higher up.
*cough* sw frontbuffer tracking *cough*
At least with fbc we have this nice igt test already.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-08-04 8:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 16:26 [PATCH 1/2] drm/i915: Introduce FBC False Color for debug purposes Rodrigo Vivi
2014-07-30 16:26 ` [PATCH 2/2] drm/i915: FBC flush nuke for BDW Rodrigo Vivi
2014-07-31 19:07 ` [PATCH] " Rodrigo Vivi
2014-08-01 14:07 ` Ville Syrjälä
2014-08-04 8:11 ` Daniel Vetter [this message]
2014-08-04 10:51 ` Rodrigo Vivi
2014-08-07 20:04 ` Rodrigo Vivi
2014-08-08 7:06 ` Daniel Vetter
[not found] ` <CABVU7+tzGz9DaKiyg_KBegcrOWhXmHWD0xGjcaRpWHGyzRcjsA@mail.gmail.com>
[not found] ` <CAKMK7uH-PipHvNFNmgD4=_W=AhmcDVejf8MN6D9-17K4nLsDzw@mail.gmail.com>
2014-08-19 18:58 ` Daniel Vetter
2014-08-21 16:44 ` Rodrigo Vivi
2014-08-26 0:39 ` Rodrigo Vivi
2014-08-26 7:54 ` Daniel Vetter
2014-08-26 18:38 ` Rodrigo Vivi
2014-08-26 20:43 ` Daniel Vetter
2014-09-05 18:28 ` Paulo Zanoni
2014-09-05 19:35 ` Rodrigo Vivi
2014-09-05 21:12 ` Rodrigo Vivi
2014-09-08 7:29 ` Daniel Vetter
2014-09-08 7:26 ` Daniel Vetter
2014-07-31 4:01 ` [PATCH 1/2] drm/i915: Introduce FBC False Color for debug purposes Ben Widawsky
2014-07-31 19:07 ` [PATCH] " Rodrigo Vivi
2014-08-01 10:27 ` Ville Syrjälä
2014-08-01 9:04 ` Rodrigo Vivi
2014-08-04 8:14 ` Daniel Vetter
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=20140804081147.GL8727@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=ville.syrjala@linux.intel.com \
/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