public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915/hsw: Add I915_EXEC_RESOURCE_STREAMER flag
Date: Wed, 9 Oct 2013 22:33:43 +0200	[thread overview]
Message-ID: <20131009203343.GR8303@phenom.ffwll.local> (raw)
In-Reply-To: <20131008233831.GC27157@bwidawsk.net>

On Tue, Oct 08, 2013 at 04:38:31PM -0700, Ben Widawsky wrote:
> On Tue, Oct 08, 2013 at 10:50:50PM +0100, Chris Wilson wrote:
> > On Wed, Oct 09, 2013 at 12:09:51AM +0300, Abdiel Janulgue wrote:
> > > Ensures that the batch buffer is executed by the resource streamer.
> > > 
> > > Signed-off-by: Abdiel Janulgue <abdiel.janulgue@linux.intel.com>
> > > ---
> > >  drivers/gpu/drm/i915/i915_gem_execbuffer.c |    2 ++
> > >  include/uapi/drm/i915_drm.h                |    5 +++++
> > >  2 files changed, 7 insertions(+)
> > > 
> > > diff --git a/drivers/gpu/drm/i915/i915_gem_execbuffer.c b/drivers/gpu/drm/i915/i915_gem_execbuffer.c
> > > index 0ce0d47..4a56c58 100644
> > > --- a/drivers/gpu/drm/i915/i915_gem_execbuffer.c
> > > +++ b/drivers/gpu/drm/i915/i915_gem_execbuffer.c
> > > @@ -962,6 +962,8 @@ i915_gem_do_execbuffer(struct drm_device *dev, void *data,
> > >  	case I915_EXEC_DEFAULT:
> > >  	case I915_EXEC_RENDER:
> > >  		ring = &dev_priv->ring[RCS];
> > > +		flags |= (args->flags & I915_EXEC_RESOURCE_STREAMER) ?
> > > +		  I915_EXEC_RESOURCE_STREAMER : 0;
> > 
> > Besides this being flags |= args->flags & I915_EXEC_RESOURCE_STREAMER;
> > flags is a completely different bitfield and you should be translating
> > into a dispatch value rather than the execbuffer value.
> > -Chris
> > 
> 
> To decrypt Chris just a bit, though he was rather more verbose than
> usual ;-), see the translation of I915_EXEC_SECURE to
> I915_DISPATCH_SECURE.

Also an i-g-t testcase which checks that we correctly reject this flag
would be good (i.e. reject it on non-render rings and on platforms that
don't support the resource streamer). We don't yet have any execbuf flags
tests at all, so this is a good opportunity to fix this.

I've tried to sign up Abdiel for this on Jira, but he's not there ...
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2013-10-09 20:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08 21:09 drm/i915/hsw: Enable resource streamer (v2) Abdiel Janulgue
2013-10-08 21:09 ` [PATCH 1/2] drm/i915/hsw: Add I915_EXEC_RESOURCE_STREAMER flag Abdiel Janulgue
2013-10-08 21:50   ` Chris Wilson
2013-10-08 23:38     ` Ben Widawsky
2013-10-09 20:33       ` Daniel Vetter [this message]
2013-10-09 21:40   ` Kenneth Graunke
2013-10-10 10:54   ` [PATCH 1/2] drm/i915/hsw: Add I915_EXEC_RESOURCE_STREAMER flag (v3) Abdiel Janulgue
2013-10-08 21:09 ` [PATCH 2/2] drm/i915/hsw: Enable resource streamer bit on MI_BATCH_BUFFER_START Abdiel Janulgue
2013-10-10 11:03   ` [PATCH 2/2] drm/i915/hsw: Enable resource streamer bit on MI_BATCH_BUFFER_START (v3) Abdiel Janulgue
2013-10-10 11:06     ` Chris Wilson

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=20131009203343.GR8303@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=ben@bwidawsk.net \
    --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