From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [patch 1/3] QEMU/KVM: separate thread for IO handling Date: Thu, 27 Mar 2008 17:49:47 +0200 Message-ID: <47EBC21B.9030907@qumranet.com> References: <20080327150906.699073229@localhost.localdomain> <20080327151016.796495237@localhost.localdomain> <47EBBBFA.9070508@qumranet.com> <20080327154859.GA8184@dmt> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel To: Marcelo Tosatti Return-path: In-Reply-To: <20080327154859.GA8184@dmt> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org 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