Marcelo Tosatti wrote: >>> >>> >> I still don't understand this. Timer expiration ought to be processed >> in the iothread, when SIGALRM is dequeued, and be completely unrelated >> to whatever vcpu 0 is doing. >> > > Yes, now it is unrelated. But before the patch it wasnt. So "currently > the SIGALRM handler..." means the current code in kvm-userspace.git. > >
I see now. Okay, will merge. >>> - Processing of IO events will not be unnecessarily interrupted. >>> >>> >> What do you mean by this? >> > > That SIGIO, SIGALRM and SIGUSR2 signals will not interrupt > main_loop_wait(), since they are now blocked. Better latency, less time > holding the mutex lock Signals are blocked in current git, they can only interrupt the guest, not the host. -- 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
