We neither report any unfinished operations during releasing GEM objects
associated with the file, and even if we did, it is bad form to report
-EINTR from a close().
The root cause of the bug that first showed itself during close is that
we do not do proper live tracking of vma and contexts
On Wed, Apr 09, 2014 at 08:03:39AM +0100, Chris Wilson wrote:
We neither report any unfinished operations during releasing GEM objects
associated with the file, and even if we did, it is bad form to report
-EINTR from a close().
The root cause of the bug that first showed itself during close
On Wed, Apr 09, 2014 at 04:49:02PM +0200, Daniel Vetter wrote:
On Wed, Apr 09, 2014 at 08:03:39AM +0100, Chris Wilson wrote:
We neither report any unfinished operations during releasing GEM objects
associated with the file, and even if we did, it is bad form to report
-EINTR from a close().
On Wed, Apr 09, 2014 at 04:03:23PM +0100, Chris Wilson wrote:
On Wed, Apr 09, 2014 at 04:49:02PM +0200, Daniel Vetter wrote:
On Wed, Apr 09, 2014 at 08:03:39AM +0100, Chris Wilson wrote:
We neither report any unfinished operations during releasing GEM objects
associated with the file, and
On Wed, Apr 09, 2014 at 06:50:03PM +0200, Daniel Vetter wrote:
On Wed, Apr 09, 2014 at 04:03:23PM +0100, Chris Wilson wrote:
On Wed, Apr 09, 2014 at 04:49:02PM +0200, Daniel Vetter wrote:
On Wed, Apr 09, 2014 at 08:03:39AM +0100, Chris Wilson wrote:
We neither report any unfinished
On Wed, Apr 09, 2014 at 08:03:39AM +0100, Chris Wilson wrote:
We neither report any unfinished operations during releasing GEM objects
associated with the file, and even if we did, it is bad form to report
-EINTR from a close().
The root cause of the bug that first showed itself during close
On Wed, Apr 09, 2014 at 10:43:47AM -0700, Ben Widawsky wrote:
On Wed, Apr 09, 2014 at 08:03:39AM +0100, Chris Wilson wrote:
We neither report any unfinished operations during releasing GEM objects
associated with the file, and even if we did, it is bad form to report
-EINTR from a close().