Vignatti Tiago (Nokia-MS/Helsinki) wrote: > Yep, makes sense. However Peter mentioned a good point: that drivers will want > to know if the server is assuming thread or SIGIO, mostly to do malloc tricks > I guess. So we may want to just drop off the SIGIO code for once and enable > always the threaded coded. > > I'm wondering how this sounds for other platforms (I'm coding in Linux) and > other DDX. Alan, Mark Kettenis, Jon Turney and others?
SIGIO is currently disabled by default on Solaris, due to the "hilarious" FP register bug in our signal handler context [1] ajax mentioned. I don't think we do anything special for SIGIO or not, just try not to call signal-unsafe functions from functions that may be in a signal handler. Certain code paths get simpler if that's never an issue. [1] http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6859428 -- -Alan Coopersmith- alan.coopersm...@oracle.com Oracle Solaris Platform Engineering: X Window System _______________________________________________ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
