From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [igt-dev] [Intel-gfx] [PATCH i-g-t] igt/gem_unfence_active_buffers: Check GEM before use
Date: Thu, 12 Jul 2018 22:01:59 +0300 [thread overview]
Message-ID: <20180712190159.GH5565@intel.com> (raw)
In-Reply-To: <20180712154003.12630-1-chris@chris-wilson.co.uk>
On Thu, Jul 12, 2018 at 04:40:03PM +0100, Chris Wilson wrote:
> As we want to make the buffers active on the GPU before removing their
> fence, an operational GPU (not wedged!) is required.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> tests/gem_unfence_active_buffers.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tests/gem_unfence_active_buffers.c b/tests/gem_unfence_active_buffers.c
> index 6df23cc53..b78fbafa7 100644
> --- a/tests/gem_unfence_active_buffers.c
> +++ b/tests/gem_unfence_active_buffers.c
> @@ -74,6 +74,7 @@ igt_simple_main
> data[i] = i;
>
> fd = drm_open_driver(DRIVER_INTEL);
> + igt_require_gem(fd);
>
> bufmgr = drm_intel_bufmgr_gem_init(fd, 4096);
> drm_intel_bufmgr_gem_enable_reuse(bufmgr);
> --
> 2.18.0
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-07-12 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 15:40 [Intel-gfx] [PATCH i-g-t] igt/gem_unfence_active_buffers: Check GEM before use Chris Wilson
2018-07-12 19:01 ` Ville Syrjälä [this message]
2018-07-12 19:04 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2018-07-12 22:41 ` [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=20180712190159.GH5565@intel.com \
--to=ville.syrjala@linux.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;
as well as URLs for NNTP newsgroup(s).