All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Nick Hoath <nicholas.hoath@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/4] drm/i915: Subsume intel_ctx_submit_request in to drm_i915_gem_request
Date: Wed, 17 Dec 2014 21:42:46 +0100	[thread overview]
Message-ID: <20141217204246.GG2711@phenom.ffwll.local> (raw)
In-Reply-To: <20141217203946.GF2711@phenom.ffwll.local>

On Wed, Dec 17, 2014 at 09:39:46PM +0100, Daniel Vetter wrote:
> On Tue, Dec 16, 2014 at 12:32:30PM +0000, Nick Hoath wrote:
> > diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> > index d68c75f..114adc3 100644
> > --- a/drivers/gpu/drm/i915/i915_drv.h
> > +++ b/drivers/gpu/drm/i915/i915_drv.h
> > @@ -2036,6 +2036,30 @@ struct drm_i915_gem_request {
> >  	struct list_head client_list;
> >  
> >  	uint32_t uniq;
> > +
> > +	/**
> > +	 * The ELSP only accepts two elements at a time, so we queue
> > +	 * context/tail pairs on a given queue (ring->execlist_queue) until the
> > +	 * hardware is available. The queue serves a double purpose: we also use
> > +	 * it to keep track of the up to 2 contexts currently in the hardware
> > +	 * (usually one in execution and the other queued up by the GPU): We
> > +	 * only remove elements from the head
> > +	 * of the queue when the hardware informs us that an element has been
> > +	 * completed.
> > +	 *
> > +	 * All accesses to the queue are mediated by a spinlock
> > +	 * (ring->execlist_lock).
> > +	 */
> > +
> > +	/** Execlist link in the submission queue.*/
> > +	struct list_head execlist_link;
> > +
> > +	/** Execlists workqueue for processing this request in a bottom half */
> > +	struct work_struct work;
> 
> Hm I've thought this would drop out with the other rework we've had
> floating around. It's also not used anywhere, so I guess it disappeared
> for real and is just a leftover from rebasing?

And a plea from your maintainer: I've asked for exactly this in my reply,
but there was no reply from you nor any mention about anything in the
in-patch changelog. So I had to digg through all the patches and the old
thread to figure out again what it is my subconscious told me is missing.

This isn't efficient, so please always acknowledge review feedbacka and
questions either with a reply or in the commit message changelogs (there
it needs the name of the reviewer in case there was lots of feedback.)

Thanks, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2014-12-17 20:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16 12:32 [PATCH 0/4] drm/i915: Untangle execlist tracking Nick Hoath
2014-12-16 12:32 ` [PATCH 1/4] drm/i915: execlist request keeps ptr/ref to gem_request Nick Hoath
2014-12-16 12:32 ` [PATCH 2/4] drm/i915: Removed duplicate members from submit_request Nick Hoath
2014-12-16 12:32 ` [PATCH 3/4] drm/i915: Remove FIXME_lrc_ctx backpointer Nick Hoath
2014-12-16 12:32 ` [PATCH 4/4] drm/i915: Subsume intel_ctx_submit_request in to drm_i915_gem_request Nick Hoath
2014-12-16 17:49   ` shuang.he
2014-12-17 20:39   ` Daniel Vetter
2014-12-17 20:42     ` Daniel Vetter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-12-22  9:37 [PATCH 0/4] drm/i915: Untangle execlist tracking Nick Hoath
2014-12-22  9:37 ` [PATCH 4/4] drm/i915: Subsume intel_ctx_submit_request in to drm_i915_gem_request Nick Hoath
2015-01-12 15:33 [PATCH 0/4] drm/i915: Untangle execlist tracking Nick Hoath
2015-01-12 15:33 ` [PATCH 4/4] drm/i915: Subsume intel_ctx_submit_request in to drm_i915_gem_request Nick Hoath
2015-01-12 21:19   ` shuang.he
2015-01-15 13:10 [PATCH 0/4] drm/i915: Untangle execlist tracking Nick Hoath
2015-01-15 13:10 ` [PATCH 4/4] drm/i915: Subsume intel_ctx_submit_request in to drm_i915_gem_request Nick Hoath
2015-01-16  7:23   ` shuang.he
2015-01-29 15:42   ` Tvrtko Ursulin

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=20141217204246.GG2711@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=nicholas.hoath@intel.com \
    /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.