From: Matthew Auld <matthew.auld@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] prime_busy: Prebind the batch buffer
Date: Thu, 22 Aug 2019 10:54:41 +0100 [thread overview]
Message-ID: <23c7ce66-c95d-b449-d498-2a20507e1e36@intel.com> (raw)
In-Reply-To: <20190821200328.22668-1-chris@chris-wilson.co.uk>
On 21/08/2019 21:03, Chris Wilson wrote:
> The test assumes that the dmabuf for the batch buffer has no exclusive
> fence. This is only true for the batch as it executes on the GPU; prior
> to that we may be in the process of moving it into memory and the
> ppGTT which cause the batch to carry an exclusive fence. Keep the test
> simple and prebind the batch buffer so that when we poll the dmabuf fd,
> we only expect it to be the spinning batch.
>
> Alternatively we could wait until we start writing values into scratch
> (i.e. igt_spin_busywait_until_started()). This seemed simpler.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Matthew Auld <matthew.auld@intel.com>
Acked-by: Matthew Auld <matthew.auld@intel.com>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-08-22 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 20:03 [igt-dev] [PATCH i-g-t] prime_busy: Prebind the batch buffer Chris Wilson
2019-08-21 21:01 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-08-22 9:54 ` Matthew Auld [this message]
2019-08-22 10:54 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=23c7ce66-c95d-b449-d498-2a20507e1e36@intel.com \
--to=matthew.auld@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--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