All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: fix rsvd2 mask when out-fence is returned
Date: Wed, 14 Feb 2018 21:45:03 +0000	[thread overview]
Message-ID: <151864470304.15373.8174996879138515397@mail.alporthouse.com> (raw)
In-Reply-To: <20180214191827.8465-1-daniele.ceraolospurio@intel.com>

Quoting Daniele Ceraolo Spurio (2018-02-14 19:18:25)
> GENMASK_ULL wants the high bit of the mask first. The current value
> cancels the in-fence when an out-fence is returned
> 
> Fixes: fec0445caa273 ("drm/i915: Support explicit fencing for execbuf")
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>

Pushed, thanks for the fix and the test case.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2018-02-14 21:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 19:18 [PATCH] drm/i915: fix rsvd2 mask when out-fence is returned Daniele Ceraolo Spurio
2018-02-14 19:18 ` [PATCH i-g-t] tests/gem_exec_fence: test that in-fence is not overwritten Daniele Ceraolo Spurio
2018-02-14 19:29   ` Chris Wilson
2018-02-14 19:34     ` Chris Wilson
2018-02-14 19:24 ` [PATCH] drm/i915: fix rsvd2 mask when out-fence is returned Chris Wilson
2018-02-14 20:49 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-02-14 21:45 ` Chris Wilson [this message]
2018-02-14 23:00 ` ✗ Fi.CI.BAT: failure for tests/gem_exec_fence: test that in-fence is not overwritten Patchwork
2018-02-15  4:55 ` ✓ Fi.CI.IGT: success for drm/i915: fix rsvd2 mask when out-fence is returned 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=151864470304.15373.8174996879138515397@mail.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=daniele.ceraolospurio@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.