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] Control tools work

To: Charles Coffing <ccoffing@xxxxxxxxxx>
Subject: Re: [Xen-devel] Control tools work
From: Christian Limpach <Christian.Limpach@xxxxxxxxxxxx>
Date: Wed, 1 Jun 2005 21:13:06 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 01 Jun 2005 20:12:22 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <s29d6a51.010@xxxxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <s29d6a51.010@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Wed, Jun 01, 2005 at 07:56:54AM -0600, Charles Coffing wrote:
> > [1] I think I'll make the control pipe and error/progress reporting 
> > filehandles function call arguments to make it easier to use 
> > {save,restore} when you link libxc into your application. 
> > Although I really think you want to run these in a seperate process to 
> > isolate them from your main application.  If there's real demand we 
> > could bring back something like ioctxt to give you callbacks for 
> > control/error/progress. 
> Is there a specific reason you suggest running these in a separate
> process?  I'm wondering if this is just a general preference because
> isolation tends to be a good thing, or if you suspect, say, a
> maliciously crafted domain could somehow crash the domain builder
> function.

I suspect not all error paths to be well tested.


Xen-devel mailing list

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