From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:60846) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SlFNv-0003PN-QG for qemu-devel@nongnu.org; Sun, 01 Jul 2012 04:20:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SlFNt-0005iP-Ql for qemu-devel@nongnu.org; Sun, 01 Jul 2012 04:19:59 -0400 Received: from mx1.redhat.com ([209.132.183.28]:22991) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SlFNt-0005iL-Ia for qemu-devel@nongnu.org; Sun, 01 Jul 2012 04:19:57 -0400 Message-ID: <4FF00825.7090606@redhat.com> Date: Sun, 01 Jul 2012 11:19:49 +0300 From: Avi Kivity MIME-Version: 1.0 References: <4FEC56B2.6050502@dlhnet.de> <4FEC5B5A.4060302@siemens.com> <4FEC7214.2020900@dlhnet.de> <4FEC76A8.6060100@siemens.com> <4FEC866F.5000402@dlhnet.de> <4FEC8722.7070301@redhat.com> <7C6F41F3-D0BC-4753-853D-E68B2AAAAADB@dlhnet.de> In-Reply-To: <7C6F41F3-D0BC-4753-853D-E68B2AAAAADB@dlhnet.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] qemu-kvm-1.0.1 - unable to exit if vcpu is in infinite loop List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Lieven Cc: Jan Kiszka , "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" On 06/28/2012 10:27 PM, Peter Lieven wrote: > > Am 28.06.2012 um 18:32 schrieb Avi Kivity: > >> On 06/28/2012 07:29 PM, Peter Lieven wrote: >>>> Yes. A signal is sent, and KVM returns from the guest to userspace on >>>> pending signals. >> >>> is there a description available how this process exactly works? >> >> The kernel part is in vcpu_enter_guest(), see the check for >> signal_pending(). But this hasn't seen changes for quite a long while. > > Thank you, i will have a look. I noticed a few patches that where submitted > during the last year, maybe one of them is related: > > Switch SIG_IPI to SIGUSR1 > Fix signal handling of SIG_IPI when io-thread is enabled > > In the first commit there is mentioned a "32-on-64-bit Linux kernel bug" > is there any reference to that? http://web.archiveorange.com/archive/v/1XS1vwGSFLyYygwTXg1K. Are you running 32-on-64? -- error compiling committee.c: too many arguments to function