From: Chris Wilson <chris@chris-wilson.co.uk>
To: Peter Clifton <pcjc2@cam.ac.uk>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] intel: Fix emit_linear_blit to use DWORD aligned width blits
Date: Tue, 09 Nov 2010 11:43:58 +0000 [thread overview]
Message-ID: <c6d829$pg1b6s@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <1289302492.2999.16.camel@pcjc2lap>
On Tue, 09 Nov 2010 11:34:52 +0000, Peter Clifton <pcjc2@cam.ac.uk> wrote:
> On Tue, 2010-11-09 at 10:52 +0000, Peter Clifton wrote:
> > On Sun, 2010-11-07 at 10:25 +0000, Chris Wilson wrote:
>
> > I've not tried that yet, but the PRM does state that BLT pitch is in
> > DWORDs.
>
> Gah.. the PRM is badly written in places! In one place it states DWORDs,
> then in another you get the actual detail:
Of course, I was reading another document which made no mention of the
tiling or dword restrictions ;-)
Contradictory, uncrossreferenced, incomplete docs are all we have.
> Chris, I can try word-aligned if you wish, but am chasing some other
> random GPU hangs / crashes at the moment. Fun fun ;)
No need, life is too short.
> (PS. Any idea where batchbuffer containing 3D commands, but with a
> string of 6-8 MI_NOOP commands would come from? I can't find code to
> emit like that in MESA or the 2D driver - I am wondering if the buffer
> had become corrupted).
Keep digging and you'll find a reference to some silicon bugs for which
certain commands (in this case it's probably the URB_FENCE) must not cross
cache-lines. I'm guessing that the MI_NOOPs you've seen are due to us
aligning the following commands to meet such constraints.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-11-09 11:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 10:04 [PATCH] intel: Fix emit_linear_blit to use DWORD aligned width blits Peter Clifton
2010-11-07 10:25 ` Chris Wilson
2010-11-09 10:52 ` Peter Clifton
2010-11-09 11:34 ` Peter Clifton
2010-11-09 11:43 ` Chris Wilson [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-11-06 9:23 Peter Clifton
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='c6d829$pg1b6s@fmsmga001.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=pcjc2@cam.ac.uk \
/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