Re: [RFC v2] drm/i915: Android native sync support

From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <Intel-gfx@lists.freedesktop.org>
Subject: Re: [RFC v2] drm/i915: Android native sync support
Date: Mon, 26 Jan 2015 11:08:43 +0000	[thread overview]
Message-ID: <54C6203B.7080404@linux.intel.com> (raw)
In-Reply-To: <CAKMK7uHd4ZNOWDFaVtR7oupZMo1ra3pCxszCoYdth1BeNM_Cxw@mail.gmail.com>

On 01/24/2015 09:47 AM, Daniel Vetter wrote:
> On Fri, Jan 23, 2015 at 5:49 PM, Tvrtko Ursulin
> <tvrtko.ursulin@linux.intel.com> wrote:
>> Could you please translate this into something understandable by newcomers?
>> :)
>
> I don't know which parts are confusing without questions so please ask
> them ... the questions below about scheduler interactions seem fairly
> advanced ;-)

I suppose for starters, when I took over this work I read the last 
thread from December.  There you were saying to Jesse to convert the 
separate ioctl into execbuf interface for in & out fences.

That's what I did I thought. So is that not the fashion of the day any 
more or I misunderstood something?

People will scream very soon for something along these lines anyway 
since it is kind of packaged with the scheduler I am told and both will 
be very much desired soon.

Idea is to allow submitting of work and not block in userspace rather 
let the scheduler queue and shuffle depending on fences.

Regards,

Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx