From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Pending signals prevent entry to the guest Date: Wed, 21 Jan 2009 10:49:50 +0200 Message-ID: <4976E1AE.6060801@redhat.com> References: <9780058.34741232510963338.JavaMail.root@mailserv1> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm To: Steven Stovall Return-path: Received: from mx2.redhat.com ([66.187.237.31]:33626 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1764197AbZAUIt7 (ORCPT ); Wed, 21 Jan 2009 03:49:59 -0500 In-Reply-To: <9780058.34741232510963338.JavaMail.root@mailserv1> Sender: kvm-owner@vger.kernel.org List-ID: Steven Stovall wrote: > I posted about a week ago regarding a very different behavior with a host-side app vis a vis kvm-77 vs kvm-33. Pending signals (SIGIO and SIGALRM) never seem to be dequeued so that I never kvm_guest_enter()...it appears that only the dynticks alarm_timer gets enabled which only handles SIGALRM, while the rtc alarm_timer which handles SIGIO does not. I have tried to make sure both are enabled, but I still have perpetual pending signals...is this possible?? Or is there some corruption somewhere? > You must call sigtimedwait() or one of its friends with the pending signal enabled after KVM_VCPU_RUN exits with -EINTR. -- error compiling committee.c: too many arguments to function