qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: xen-devel@lists.xensource.com
Subject: Re: [Qemu-devel] [PATCH 01/11] Handle terminating signals.
Date: Mon, 11 Aug 2008 20:53:02 -0500	[thread overview]
Message-ID: <48A0ECFE.2040703@codemonkey.ws> (raw)
In-Reply-To: <48A099ED.6050303@redhat.com>

Gerd Hoffmann wrote:
> Anthony Liguori wrote:
>   
>> Gerd Hoffmann wrote:
>>     
>>> +void fatalsig_register_handler(void (*func)(void));
>>>   
>>>       
>> Unless I'm misreading, none of your patches seem to use this function. 
>> What are you adding this mechanism for?
>>     
>
> The patch using that isn't fully polished yet for submission.  Sneak
> preview is here:
>
> http://kraxel.fedorapeople.org/patches/qemu-upstream/0015-xen-domain-builder.patch
>
> Adds pv domain builder to qemu, so you can start pv xen guests using
> qemu only.  In that case we'll want to destroy the guest domain when
> qemu goes down because the xen management stack will not cleanup after us.
>   

I was asking because I thought it may be something like this.  An 
alternative to this signal handler stuff would be to fork() off a 
process with another end of a pipe.  That process could just sit their 
waiting for eof and when eof was received, it could destroy the domain.

The main advantage of this approach is that it works in every possible 
circumstance.  Even if the qemu process totally borks it's stack or 
tramples over memory in such a way as to render the signal handling code 
broken.

Regards,

Anthony Liguori

> cheers,
>   Gerd
>
>   

  reply	other threads:[~2008-08-12  1:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-11 12:32 [Qemu-devel] [PATCH 00/11] merge some xen bits into qemu Gerd Hoffmann
2008-08-11 12:32 ` [Qemu-devel] [PATCH 01/11] Handle terminating signals Gerd Hoffmann
2008-08-11 19:27   ` Anthony Liguori
2008-08-11 19:52     ` Gerd Hoffmann
2008-08-11 19:30   ` Anthony Liguori
2008-08-11 19:58     ` Gerd Hoffmann
2008-08-12  1:53       ` Anthony Liguori [this message]
2008-08-11 12:32 ` [Qemu-devel] [PATCH 02/11] add DisplayState->idle Gerd Hoffmann
2008-08-11 12:36   ` [Qemu-devel] " Samuel Thibault
2008-08-11 12:32 ` [Qemu-devel] [PATCH 03/11] add container_of() macro to osdep.h Gerd Hoffmann
2008-08-11 12:32 ` [Qemu-devel] [PATCH 04/11] move GUI_REFRESH_INTERVAL define from vl.c to console.h Gerd Hoffmann
2008-08-11 12:32 ` [Qemu-devel] [PATCH 05/11] xen: groundwork for xen support Gerd Hoffmann
2008-08-11 12:32 ` [Qemu-devel] [PATCH 06/11] xen: backend driver core Gerd Hoffmann
2008-08-11 12:32 ` [Qemu-devel] [PATCH 07/11] xen: add console backend driver Gerd Hoffmann
2008-08-11 12:32 ` [Qemu-devel] [PATCH 08/11] xen: add framebuffer " Gerd Hoffmann
2008-08-11 12:32 ` [Qemu-devel] [PATCH 09/11] xen: add block device " Gerd Hoffmann
2008-08-11 12:32 ` [Qemu-devel] [PATCH 10/11] xen: add net " Gerd Hoffmann
2008-08-11 12:32 ` [Qemu-devel] [PATCH 11/11] xen: blk & nic configuration via cmd line Gerd Hoffmann

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=48A0ECFE.2040703@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    --cc=xen-devel@lists.xensource.com \
    /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).