On Thu, 27 May 2010, Matthew Garrett wrote: > > > Doesn't help - I may be hit by the signal between the poll() unblocking > > > and me having the opportunity to call sigmask(). > > > > ppoll(). This is all existing solved stuff. > > Isn't that the inverse of what we want? The application should default > to being SIGSTOPpable except in the case of it being in the process of > having a specific event delivered. Would it help to divide the application into two processes, one of which receives events and the other does the drawing? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
