From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] tests/gem_ringfill: Exercise all rings
Date: Mon, 20 Feb 2012 22:45:40 +0000 [thread overview]
Message-ID: <e39f63$3pjiq3@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <1329776520-10968-1-git-send-email-chris@chris-wilson.co.uk>
On Mon, 20 Feb 2012 22:22:00 +0000, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On SandyBridge, the BLT commands were split from the RENDER commands as
> well as the BSD split inherited from Ironlake. So we need to make sure
> we do exercise each ring, and in order to do so we also need to make
> sure each batch takes longer to execute than it takes for us to
> submit it.
Whilst this found the bug, it does presume the BLT and RENDER copy are
equally fast. So on a SNB without the autoreported head, it fails to
fill the BLT ring as the untiled RENDER copy is far too slow.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-02-20 22:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c55c5d18l92@AZSMGA002.ch.intel.com>
2012-02-20 22:22 ` [PATCH] tests/gem_ringfill: Exercise all rings Chris Wilson
2012-02-20 22:45 ` Chris Wilson [this message]
2012-02-20 22:53 ` Chris Wilson
2012-02-22 9:55 ` 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='e39f63$3pjiq3@fmsmga002.fm.intel.com' \
--to=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