Re: [PATCH v2 2/2] dma-buf/sw_sync: force signal all unsignaled fences on dying timeline

2017-09-08 Thread Chris Wilson
Quoting Gustavo Padovan (2017-09-08 14:03:00) > Hi Chris, > > 2017-09-07 Chris Wilson : > > > Quoting Gustavo Padovan (2017-09-07 20:02:46) > > > From: Dominik Behr > > > > > > To avoid hanging userspace components that might have been waiting on

Re: [PATCH v2 2/2] dma-buf/sw_sync: force signal all unsignaled fences on dying timeline

2017-09-08 Thread Gustavo Padovan
Hi Chris, 2017-09-07 Chris Wilson : > Quoting Gustavo Padovan (2017-09-07 20:02:46) > > From: Dominik Behr > > > > To avoid hanging userspace components that might have been waiting on the > > active fences of the destroyed timeline we need to

Re: [PATCH v2 2/2] dma-buf/sw_sync: force signal all unsignaled fences on dying timeline

2017-09-07 Thread Chris Wilson
Quoting Gustavo Padovan (2017-09-07 20:02:46) > From: Dominik Behr > > To avoid hanging userspace components that might have been waiting on the > active fences of the destroyed timeline we need to signal with error all > remaining fences on such timeline. > > This restore

[PATCH v2 2/2] dma-buf/sw_sync: force signal all unsignaled fences on dying timeline

2017-09-07 Thread Gustavo Padovan
From: Dominik Behr To avoid hanging userspace components that might have been waiting on the active fences of the destroyed timeline we need to signal with error all remaining fences on such timeline. This restore the default behaviour of the Android sw_sync framework, which