WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [RFC][PATCH] Use ioemu block drivers through blktap

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Kevin Wolf <kwolf@xxxxxxx>
Subject: Re: [Xen-devel] [RFC][PATCH] Use ioemu block drivers through blktap
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Mon, 31 Mar 2008 14:31:47 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 31 Mar 2008 06:33:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <18416.58810.250091.262660@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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AciTM5FGz85EWv8mEdy9kgAX8io7RQ==
Thread-topic: [Xen-devel] [RFC][PATCH] Use ioemu block drivers through blktap
User-agent: Microsoft-Entourage/11.4.0.080122
On 31/3/08 14:23, "Ian Jackson" <Ian.Jackson@xxxxxxxxxxxxx> wrote:

>> I think in your classification they are "not really necessary" cleanups.
>> But that's no reason not to do them, right?
> 
> Yes, but to avoid gradually accumulating an ever increasing amount of
> cruft, that cleanup mechanism ought to be capable of cleaning up even
> `lost' garbage of one kind or another.  And once you've got such a
> garbage collecting cleanup arrangement, you don't need any separate
> atexit-like arrangement which cleans up specifically after the current
> run.

The SIGHUP was only introduced in the first place to allow cleanup when
using stub domains. In that case the SIGHUP goes to a qemu-dm 'proxy script'
which then kills the actual stub domain. That's another case where the
mechanism for tearing down such pervasive state really belongs in xend, in
my opinion. I would be very much up for seeing us going back to SIGKILL of
qemu-dm processes.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel