diff options
author | Dave Airlie <[email protected]> | 2011-05-15 16:41:54 +1000 |
---|---|---|
committer | Dave Airlie <[email protected]> | 2011-05-16 06:40:26 +1000 |
commit | bc16c73407d11bb6702cf7de9925bfaeb80a5272 (patch) | |
tree | 12ee481ed773ffb80d695f6c50097cb7b91af544 /src/mesa/state_tracker/st_context.h | |
parent | bd5b7a6f7113da38a2c1f07a4a71e9993666a567 (diff) |
gallium: block signals for new thread when spawning threads
I'm hard pressed to think of any reason a gallium thread would want to
receive a signal, especially considering its probably loaded as a library
and you don't want the threads interfering with the main threads signal
handling.
This solves a problem loading llvmpipe into the X server for AIGLX,
where the X server relies on the SIGIO signal going to the main thread,
but once llvmpipe loads the SIGIO can end up in any of its threads.
Signed-off-by: Dave Airlie <[email protected]>
Diffstat (limited to 'src/mesa/state_tracker/st_context.h')
0 files changed, 0 insertions, 0 deletions