All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Graunke <kenneth@whitecape.org>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [Mesa-dev] [PATCH 1/2] i965: Make intel_emit_linear_blit handle Gen8+ alignment restrictions.
Date: Wed, 06 May 2015 10:41:34 -0700	[thread overview]
Message-ID: <30445906.Uy24vLNqI1@eiger> (raw)
In-Reply-To: <877fslzkhj.fsf@gaia.fi.intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 1905 bytes --]

On Wednesday, May 06, 2015 08:25:28 PM Mika Kuoppala wrote:
> Chris Wilson <chris@chris-wilson.co.uk> writes:
> 
> > On Wed, May 06, 2015 at 03:38:44PM +0200, Daniel Vetter wrote:
> >> On Tue, Apr 21, 2015 at 10:13:31PM -0700, Kenneth Graunke wrote:
> >> > The BLT engine on Gen8+ requires linear surfaces to be cacheline
> >> > aligned.  This restriction was added as part of converting the BLT to
> >> > use 48-bit addressing.
> >> > 
> >> > intel_emit_linear_blit needs to handle blits that are not cacheline
> >> > aligned, as we use it for arbitrary glBufferSubData calls and subrange
> >> > mappings.
> >> > 
> >> > Since intel_emit_linear_blit uses 1 byte per pixel, we can use the src/dst
> >> > pixel X offset field to represent the unaligned portion, and subtract
> >> > that from the address so it's cacheline aligned.
> >> > 
> >> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=88521
> >> > Signed-off-by: Kenneth Graunke <kenneth@whitecape.org>
> >> > Cc: mesa-stable@lists.freedesktop.org
> >> 
> >> s/cacheline/page/ afaik, and nope it's not documented. Chris&Mika learned
> >> that the hard way. Adding them to correct me in case I make a mess again.
> >
> > It's cacheline.
> >
> > Issue: if the 1st pixel in XY_SRC_COPY  is not CL aligned when SRC or
> > DST are linear that will cause failure.
> >
> > https://vthsd.fm.intel.com/hsd/bdwgfx/bug_de/default.aspx?bug_de_id=1912704
> > -Chris
> >
> 
> FWIF, I ended up doing it like this in igt:
> 
> http://lists.freedesktop.org/archives/intel-gfx/2015-January/059191.html
> 
> And I think the documentation was updated on the restrictions.
> 
> -Mika

Yeah, I saw the updated documentation, remembered that Chris warned me
about this a while back (I think I just said "ugh" and promptly forgot
about it), and finally fixed Mesa.  It's all upstream and working now.

Huge thanks for tracking this down and getting it documented!

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 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

      reply	other threads:[~2015-05-06 17:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1429679612-18584-1-git-send-email-kenneth@whitecape.org>
2015-05-06 13:38 ` [Mesa-dev] [PATCH 1/2] i965: Make intel_emit_linear_blit handle Gen8+ alignment restrictions Daniel Vetter
2015-05-06 13:45   ` Chris Wilson
2015-05-06 17:25     ` Mika Kuoppala
2015-05-06 17:41       ` Kenneth Graunke [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=30445906.Uy24vLNqI1@eiger \
    --to=kenneth@whitecape.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mika.kuoppala@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 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.