public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
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: [Intel-gfx] [igt-dev] [PATCH i-g-t] igt/gem_tiled_fence_blits: Remember to mark up fence blits
Date: Tue, 30 Oct 2018 20:04:17 +0200	[thread overview]
Message-ID: <20181030180417.GD9144@intel.com> (raw)
In-Reply-To: <154092064605.1910.16450272418180690286@skylake-alporthouse-com>

On Tue, Oct 30, 2018 at 05:30:46PM +0000, Chris Wilson wrote:
> Quoting Ville Syrjälä (2018-10-30 13:32:39)
> > On Mon, Oct 29, 2018 at 08:49:58PM +0000, Chris Wilson wrote:
> > > Older platforms require fence registers to perform blits, and so
> > > userspace is expected to mark up the objects to request fences be
> > > assigned.
> > > 
> > > Fixes: ff2db94acb53 ("igt/gem_tiled_fence_blits: Remove libdrm_intel dependence")
> > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108591
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > ---
> > >  tests/i915/gem_tiled_fence_blits.c | 2 ++
> > >  1 file changed, 2 insertions(+)
> > > 
> > > diff --git a/tests/i915/gem_tiled_fence_blits.c b/tests/i915/gem_tiled_fence_blits.c
> > > index 7560fa52..e40a7b43 100644
> > > --- a/tests/i915/gem_tiled_fence_blits.c
> > > +++ b/tests/i915/gem_tiled_fence_blits.c
> > > @@ -141,6 +141,8 @@ static void run_test(int fd, int count)
> > >  
> > >       memset(reloc, 0, sizeof(reloc));
> > >       memset(obj, 0, sizeof(obj));
> > > +     obj[0].flags = EXEC_OBJECT_NEEDS_FENCE;
> > > +     obj[1].flags = EXEC_OBJECT_NEEDS_FENCE;
> > 
> > No harm in always asking for the fence I suppose.
> 
> If the fence isn't required for the GPU (i.e. gen4+) we just quietly
> pretend it was never requested.

Ah yes. I do recall that being the case. But I couldn't immediately
find the code for it. Now after a second look it seems to be this:

if (!eb->reloc_cache.has_fence) {
	entry->flags &= ~EXEC_OBJECT_NEEDS_FENCE;
} else {
	...

I guess the "reloc_cache" name threw me off the track the first time
around.

-- 
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2018-10-30 18:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-29 20:49 [Intel-gfx] [PATCH i-g-t] igt/gem_tiled_fence_blits: Remember to mark up fence blits Chris Wilson
2018-10-30  2:59 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2018-10-30 10:36 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-10-30 13:32 ` [Intel-gfx] [igt-dev] [PATCH i-g-t] " Ville Syrjälä
2018-10-30 17:30   ` Chris Wilson
2018-10-30 18:04     ` Ville Syrjälä [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=20181030180417.GD9144@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