Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-devel

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

To: Kevin Wolf <kwolf@xxxxxxx>
Subject: Re: [Xen-devel] [RFC][PATCH] Use ioemu block drivers through blktap
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Fri, 28 Mar 2008 15:22:59 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 28 Mar 2008 08:24:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <47D91D3D.1000005@xxxxxxx>
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>
Newsgroups: chiark.mail.xen.devel
References: <47D569F6.1010209@xxxxxxx> <47D91D3D.1000005@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Kevin Wolf writes ("Re: [Xen-devel] [RFC][PATCH] Use ioemu block drivers 
through blktap"):
> I've reworked and cleaned up the thing, so the attached patch should be
> much better. If you agree that my approach is the right one, I think it
> could be committed in this (or a similar) shape.

Sorry for picking this up now, but I'm trying to reconcile ioemu with
qemu and I wondered what the purpose of these changes was:

> +static void qemu_sighup_handler(int signal)
> +{
> +    fprintf(stderr, "Received SIGHUP, terminating.\n");
> +    exit(0);
> +}
> +

> -    signal(SIGHUP, SIG_DFL);
> +    signal(SIGHUP, qemu_sighup_handler);

Thanks,
Ian.

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