From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: qemu-kvm-1.0.1 - unable to exit if vcpu is in infinite loop Date: Thu, 28 Jun 2012 19:32:34 +0300 Message-ID: <4FEC8722.7070301@redhat.com> References: <4FEC56B2.6050502@dlhnet.de> <4FEC5B5A.4060302@siemens.com> <4FEC7214.2020900@dlhnet.de> <4FEC76A8.6060100@siemens.com> <4FEC866F.5000402@dlhnet.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Jan Kiszka , "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" To: Peter Lieven Return-path: Received: from mx1.redhat.com ([209.132.183.28]:62945 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753995Ab2F1Qcl (ORCPT ); Thu, 28 Jun 2012 12:32:41 -0400 In-Reply-To: <4FEC866F.5000402@dlhnet.de> Sender: kvm-owner@vger.kernel.org List-ID: 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. -- error compiling committee.c: too many arguments to function