Resending, since previous patch emails seem to have been blocked by sf. The reason for this change is twofold: 1) -ERESTART is returned to user-space, but that return-code is not available in *BSD, user-space, and we'd like to be able to reuse user-space-code. 2) -ERESTARTSYS is caught by the linux kernel signal handling layer, and the syscall is automatically restarted if possible. Otherwise, it's converted to an -EINTR and returned to user space.
The Radeon part of this patch removes the -ERESTART handling code, and instead requests non-interruptible sleeps from TTM. This is because the Radeon code never returned to user- space anyway, but was spinning in the kernel until the TTM call succeeded. Also there is a change in the Radeon code so that when fence waits are interrupted by a system call, they return -ERESTARTSYS instead of -EBUSY. This should be thoroughly reviewed. ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel