From: Daniel Vetter <daniel@ffwll.ch>
To: "Daniel, Thomas" <thomas.daniel@intel.com>
Cc: "daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 0/4] drm/i915: Untangle execlist tracking
Date: Tue, 20 Jan 2015 10:41:10 +0100 [thread overview]
Message-ID: <20150120094110.GK10113@phenom.ffwll.local> (raw)
In-Reply-To: <BFEE8FEC12424048AF1805991D65FA91197254F1@irsmsx105.ger.corp.intel.com>
On Fri, Jan 16, 2015 at 09:48:31AM +0000, Daniel, Thomas wrote:
> > -----Original Message-----
> > From: Intel-gfx [mailto:intel-gfx-bounces@lists.freedesktop.org] On Behalf
> > Of Nick Hoath
> > Sent: Thursday, January 15, 2015 1:11 PM
> > To: intel-gfx@lists.freedesktop.org
> > Cc: daniel.vetter@ffwll.ch
> > Subject: [Intel-gfx] [PATCH 0/4] drm/i915: Untangle execlist tracking
> >
> > This patchset merges execlist queue items in to gem requests. It does this by
> > using the reference count added by the "Replace seqno values with request
> > structures" patchset to ensure that the gem request is available for the
> > whole execlist submission lifespan.
> >
> > v2: merge intel_ctx_submit_request and drm_i915_gem_request, rebase
> > changes &
> > add cover letter
> >
> > v3: Rebase over upstreamed "Replace seqno values with request structures"
> > and add overzealous freeing fix.
> >
> > v4: Removed re-addition of cleanup work queue (found by Daniel Vetter)
> > v5: Fixed non-building individual patch (0002). Separated out the tail pointer
> > from the postfix pointer (found by Thomas Daniel)
> > v6: Actual removal of intel_ctx_submit_request. Update both tail and postfix
> > pointer in __i915_add_request (found by Thomas Daniel)
> > v7: Removed unrelated changes
> Well, I'm happy with v7 of this patchset now.
> Reviewed-by: Thomas Daniel <thomas.daniel@intel.com>
Entire series merged, thanks a lot for patches&review. I've reformatted
one comment in patch 4 while applying, linebreaks got screwed up a bit
somehow.
-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
next prev parent reply other threads:[~2015-01-20 9:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 13:10 [PATCH 0/4] drm/i915: Untangle execlist tracking Nick Hoath
2015-01-15 13:10 ` [PATCH 1/4] drm/i915: execlist request keeps ptr/ref to gem_request Nick Hoath
2015-01-15 13:10 ` [PATCH 2/4] drm/i915: Removed duplicate members from submit_request Nick Hoath
2015-01-15 13:10 ` [PATCH 3/4] drm/i915: Remove FIXME_lrc_ctx backpointer 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
2015-01-16 9:48 ` [PATCH 0/4] drm/i915: Untangle execlist tracking Daniel, Thomas
2015-01-20 9:41 ` Daniel Vetter [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-01-12 15:33 Nick Hoath
2014-12-22 9:37 Nick Hoath
2014-12-16 12:32 Nick Hoath
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=20150120094110.GK10113@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=thomas.daniel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox