From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Maarten Lankhorst <maarten.lankhorst@canonical.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Android sync points for i915 v2
Date: Tue, 5 Aug 2014 08:03:35 -0700 [thread overview]
Message-ID: <20140805080335.20154a8a@jbarnes-desktop> (raw)
In-Reply-To: <53E09154.8010005@canonical.com>
On Tue, 05 Aug 2014 10:09:56 +0200
Maarten Lankhorst <maarten.lankhorst@canonical.com> wrote:
> op 05-08-14 01:18, Jesse Barnes schreef:
> > Expose an ioctl to create Android fences based on the Android sync point
> > infrastructure (which in turn is based on DMA-buf fences). Just a
> > sketch at this point, no testing has been done.
> >
> > There are a couple of goals here:
> > 1) allow applications and libraries to create fences without an
> > associated buffer
> > 2) re-use a common API so userspace doesn't have to impedance mismatch
> > between different driver implementations too much
> > 3) allow applications and libraries to use explicit synchronization if
> > they choose by exposing fences directly
> >
> > v2: use struct fence directly using Maarten's new interface
>
> > diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> > index d604f4f..6eb119e 100644
> > --- a/drivers/gpu/drm/i915/i915_drv.h
> > +++ b/drivers/gpu/drm/i915/i915_drv.h
> > @@ -1388,6 +1388,8 @@ struct i915_frontbuffer_tracking {
> > unsigned flip_bits;
> > };
> >
> > +struct i915_sync_timeline;
> > +
> > struct drm_i915_private {
> > struct drm_device *dev;
> > struct kmem_cache *slab;
> > @@ -1422,6 +1424,8 @@ struct drm_i915_private {
> > struct drm_i915_gem_object *semaphore_obj;
> > uint32_t last_seqno, next_seqno;
> >
> > + struct i915_sync_timeline *sync_tl[I915_NUM_RINGS];
> > +
> > drm_dma_handle_t *status_page_dmah;
> > struct resource mch_res;
> >
> Leftover remnant?
Oops, yeah. I still need to add a way to request a fence on a specific
ring, and that ties into our context API, so that's still open. But I
definitely don't want a sync timeline here with this approach.
> I think you should rebase on top of Chris' seqno/request stuff like you said in TODO, it would reduce the patch to just the ioctl. ;-)
I need to check if it landed yet, but yes it will make things even
simpler.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-08-05 15:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 18:58 [RFC] Sync points/fences for i915 Jesse Barnes
2014-07-31 18:58 ` [PATCH] drm/i915: Android sync points " Jesse Barnes
2014-08-01 6:23 ` Maarten Lankhorst
2014-08-04 23:18 ` [PATCH] drm/i915: Android sync points for i915 v2 Jesse Barnes
2014-08-05 7:44 ` Daniel Vetter
2014-08-05 14:59 ` Jesse Barnes
2014-08-05 15:00 ` Maarten Lankhorst
2014-08-05 15:08 ` Daniel Vetter
2014-08-05 16:05 ` Jesse Barnes
2014-08-05 16:08 ` Daniel Vetter
2014-08-05 16:32 ` Jesse Barnes
2014-08-05 17:09 ` Jesse Barnes
2014-08-05 17:43 ` Daniel Vetter
2014-08-05 17:52 ` Jesse Barnes
2014-08-05 8:09 ` Maarten Lankhorst
2014-08-05 15:03 ` Jesse Barnes [this message]
2014-08-05 15:09 ` Daniel Vetter
2014-08-01 9:04 ` [PATCH] drm/i915: Android sync points for i915 Tvrtko Ursulin
2014-08-01 16:02 ` Jesse Barnes
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=20140805080335.20154a8a@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@canonical.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