Marcelo Tosatti wrote: > On Thu, Mar 27, 2008 at 05:25:20PM +0200, Avi Kivity wrote: > >> Marcelo Tosatti wrote: >> >>> SIGUSR1 has no handler, and the SIGUSR2 one does nothing useful anymore >>> (thats also true for SIGIO on tap fd, which runs host_alarm_handler >>> unnecessarily). >>> >>> >> The sigaction(); sa.sa_handler() stuff was added as a stopgap; do we >> actually need to run _any_ signal handlers? >> > > Yes, we need to run host_alarm_handler() to set ALARM_EXPIRED, so the > alarm timer gets rearmed by main_loop_wait. Thats the only one. > >
We can call it explicitly. I'm worried about the slirp code. I think I checked it once but it is sufficiently obfuscated to be worrying. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
