From: Damien Lespiau <damien.lespiau@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: daniel.vetter@intel.com, benjamin.widawsky@intel.com
Subject: Re: [PATCH intel-gpu-tools] gem_ring_sync_copy: Add a ring to ring synchronization test
Date: Tue, 4 Feb 2014 11:00:10 +0000 [thread overview]
Message-ID: <20140204110010.GC29013@strange.amr.corp.intel.com> (raw)
In-Reply-To: <1391012257-25503-1-git-send-email-damien.lespiau@intel.com>
On Wed, Jan 29, 2014 at 04:17:37PM +0000, Damien Lespiau wrote:
> +static void run_test(data_t *data, enum ring r1, enum ring r2, enum test test)
> +{
> + struct ring_ops *r1_ops = &ops[r1];
> + struct ring_ops *r2_ops = &ops[r2];
> + drm_intel_bo *a, *b, *c;
> +
> + a = bo_create(data, WIDTH, HEIGHT, 0xa);
> + b = bo_create(data, WIDTH, HEIGHT, 0xb);
> + c = bo_create(data, WIDTH, HEIGHT, 0xc);
> +
> + r1_ops->busy(data);
> + r2_ops->copy(data, a, b);
^^
r1
> +
> + switch (test) {
> + case TEST_WRITE_READ:
> + r2_ops->copy(data, b, c);
^^
> + bo_check(data, c, 0xa);
> + break;
Turns out I was copying a to b on r2, and then b to c still on r2. So
no inter-ring dependencies in that workload. Ooops.
Pushed an updated patch that copy a to b on r1 and then b to c on r2 and
verified that short-circuiting the semaphores breaks the test indeed.
--
Damien
prev parent reply other threads:[~2014-02-04 11:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 16:17 [PATCH intel-gpu-tools] gem_ring_sync_copy: Add a ring to ring synchronization test Damien Lespiau
2014-02-04 11:00 ` Damien Lespiau [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=20140204110010.GC29013@strange.amr.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=benjamin.widawsky@intel.com \
--cc=daniel.vetter@intel.com \
--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