All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Charles Coffing" <ccoffing@novell.com>
To: Christian.Limpach@cl.cam.ac.uk
Cc: xen-devel@lists.xensource.com
Subject: Re: Control tools work
Date: Wed, 01 Jun 2005 07:56:54 -0600	[thread overview]
Message-ID: <s29d6a51.011@sinclair.provo.novell.com> (raw)

Christian,

> [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.

Thanks for your explanations, by the way.

Charles

             reply	other threads:[~2005-06-01 13:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01 13:56 Charles Coffing [this message]
     [not found] <s29d6a51.010@sinclair.provo.novell.com>
2005-06-01 20:13 ` Control tools work Christian Limpach
     [not found] <s29c82f6.030@sinclair.provo.novell.com>
2005-06-01  0:15 ` Christian Limpach
  -- strict thread matches above, loose matches on Subject: below --
2005-05-31 21:29 Charles Coffing
2005-05-31 21:48 ` Daniel Stekloff
2005-05-31 22:25 ` Steven Hand
2005-06-01  0:25   ` Christian Limpach
2005-06-03  1:01 ` Anthony Liguori
2005-05-31 17:57 Charles Coffing
2005-05-31 21:07 ` Christian Limpach
2005-05-31 23:33 ` Jacob Gorm Hansen
2005-06-01 10:28   ` Grzegorz Milos

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=s29d6a51.011@sinclair.provo.novell.com \
    --to=ccoffing@novell.com \
    --cc=Christian.Limpach@cl.cam.ac.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.