kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Peter Lieven <pl@dlhnet.de>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
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	[thread overview]
Message-ID: <4FEC8722.7070301@redhat.com> (raw)
In-Reply-To: <4FEC866F.5000402@dlhnet.de>

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



  reply	other threads:[~2012-06-28 16:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28 13:05 qemu-kvm-1.0.1 - unable to exit if vcpu is in infinite loop Peter Lieven
2012-06-28 13:25 ` Jan Kiszka
2012-06-28 15:02   ` Peter Lieven
2012-06-28 15:22     ` Jan Kiszka
2012-06-28 16:29       ` Peter Lieven
2012-06-28 16:32         ` Avi Kivity [this message]
2012-06-28 19:27           ` Peter Lieven
2012-07-01  8:19             ` Avi Kivity
2012-07-01 19:18               ` Peter Lieven
2012-07-02  7:05                 ` Jan Kiszka
2012-07-02  8:12                   ` Peter Lieven
2012-08-06 15:11 ` Stefan Hajnoczi
2012-08-17 13:11   ` Jan Kiszka
2012-08-17 14:36     ` Jan Kiszka
2012-08-17 14:41       ` Jan Kiszka
2012-08-17 15:04         ` Jan Kiszka
2012-08-19  9:42           ` Avi Kivity
2012-08-21  7:21             ` Jan Kiszka
2012-08-21  8:23               ` Stefan Hajnoczi
2012-08-22 12:52                 ` Peter Lieven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FEC8722.7070301@redhat.com \
    --to=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=pl@dlhnet.de \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).