This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: [Qemu-devel] [PATCH 01/13] Handle terminating signal

To: qemu-devel@xxxxxxxxxx
Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 01/13] Handle terminating signals.
From: Anthony Liguori <anthony@xxxxxxxxxxxxx>
Date: Wed, 27 Aug 2008 12:55:25 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Jamie Lokier <jamie@xxxxxxxxxxxxx>, Gerd Hoffmann <kraxel@xxxxxxxxxx>
Delivery-date: Wed, 27 Aug 2008 10:56:35 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <18613.33339.351040.938403@xxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <18611.63711.631859.280983@xxxxxxxxxxxxxxxxxxxxxxxx> <48B4027C.1000008@xxxxxxxxxxxxx> <18612.1900.73781.314743@xxxxxxxxxxxxxxxxxxxxxxxx> <48B41B7E.40708@xxxxxxxxxxxxx> <18612.7267.832361.270651@xxxxxxxxxxxxxxxxxxxxxxxx> <48B41F55.1000909@xxxxxxxxxxxxx> <18612.8502.305043.233934@xxxxxxxxxxxxxxxxxxxxxxxx> <48B422F2.1090900@xxxxxxxxxxxxx> <20080826174729.GB25893@xxxxxxxxxxxxx> <18613.8801.187470.178088@xxxxxxxxxxxxxxxxxxxxxxxx> <20080827162719.GC25387@xxxxxxxxxxxxx> <18613.33339.351040.938403@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20080723)
Ian Jackson wrote:
Jamie Lokier writes ("Re: [Xen-devel] Re: [Qemu-devel] [PATCH 01/13] Handle 
terminating signals."):
Yes. Err, I'm not sure what effect that will have in Anthony's patch
but it probably wouldn't be good.

As I say I haven't managed to reproduce this other than in a full
qemu-dm tree (from qemu-xen).

So it may be that it is because of something I did or something the
qemu-xen code does - although it seems hard to imagine how it could
break the signal mask in the helper thread given that that thread runs
entirely glibc code, except when a signal is being delivered (and of
course the signal mask is saved and restored for signal delivery).

Perhaps the signal is being consumed in one of qemu-dm's other threads mistakenly?

What you're describing would seem like a serious bug. For a while, I was testing a version of QEMU/KVM that slept forever in select() and I never saw any instances of the signal not getting delivered.


Anthony Liguori


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>