atomic explicit fencing vs android

2015-11-14 Thread Rob Clark
On Fri, Nov 13, 2015 at 8:47 PM, Greg Hackmann wrote: > On Fri, Nov 13, 2015 at 1:47 PM, Rob Clark wrote: >> >> I suppose the philosophy here is >> that on android, surfaceflinger (userspace) is the trusted one (which >> may well be correct on some vendor kernel branches), whereas upstream >> the

atomic explicit fencing vs android

2015-11-13 Thread Greg Hackmann
On Fri, Nov 13, 2015 at 1:47 PM, Rob Clark wrote: > > I suppose the philosophy here is > that on android, surfaceflinger (userspace) is the trusted one (which > may well be correct on some vendor kernel branches), whereas upstream > the kernel is the trusted one. > To clarify, this wasn't the phi

atomic explicit fencing vs android

2015-11-13 Thread Rob Clark
Ok, this has been something on my TODO list to write up for a little while now.. but better late than never ;-) At LPC Daniel Vetter and myself were talking to Greg Hackmann and came to realize a bit of an impedance mismatch between how android display stack expects to use fences, and what Daniel