From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
To: Tim Deegan <Tim.Deegan@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
Xen Devel <xen-devel@lists.xensource.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH 0/3] libxl stubdom API cleanup
Date: Fri, 09 Jul 2010 12:05:30 +0100 [thread overview]
Message-ID: <4C37027A.5030207@eu.citrix.com> (raw)
In-Reply-To: <20100709105101.GD31695@whitby.uk.xensource.com>
On 09/07/10 11:51, Tim Deegan wrote:
> At 11:44 +0100 on 09 Jul (1278675850), Vincent Hanquez wrote:
>
>> On 09/07/10 09:17, Tim Deegan wrote:
>>
>>>> Is it necessary to pull the mechanism out along with the policy though?
>>>>
>>>>
>>> Or, if we're taking some mechanism out, couldn't we take _all_ the
>>> mechanism out?
>>>
>> Which one do you have in minds ?
>>
> It looks like your patch leaves some "create a stubdom" functions in the
> libxl API. I'd have thought libxl should either handle stubdoms
> entirely or not at all. (Unless stubdom creation needs some low-level
> grunge that will uglify the libxl API if it's exposed that far up - I
> can't think of any except PRIV_FOR though).
>
I think that either is fine from my point of view; as long as I don't
have to capture two very different semantics (starting a program |
starting a domain) in one call.
--
Vincent
next prev parent reply other threads:[~2010-07-09 11:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 13:00 [PATCH 0/3] libxl stubdom API cleanup Vincent Hanquez
2010-07-07 13:00 ` [PATCH 1/3] move stubdom make into a proper function Vincent Hanquez
2010-07-07 13:00 ` [PATCH 2/3] let the user of libxenlight choose explicitely if it want to start a stubdom or not Vincent Hanquez
2010-07-07 13:00 ` [PATCH 3/3] stubdom_create returns stubdomain domid so that unpause is done by the user of libxenlight Vincent Hanquez
2010-07-07 16:53 ` [PATCH 0/3] libxl stubdom API cleanup Stefano Stabellini
2010-07-08 11:17 ` Vincent Hanquez
2010-07-08 14:03 ` Stefano Stabellini
2010-07-08 14:18 ` Ian Campbell
2010-07-08 16:27 ` Ian Jackson
2010-07-08 17:18 ` Vincent Hanquez
2010-07-09 7:52 ` Ian Campbell
2010-07-09 8:17 ` Tim Deegan
2010-07-09 10:44 ` Vincent Hanquez
2010-07-09 10:51 ` Tim Deegan
2010-07-09 10:59 ` Stefano Stabellini
2010-07-09 14:44 ` Tim Deegan
2010-07-09 11:05 ` Vincent Hanquez [this message]
2010-07-09 17:04 ` Ian Jackson
2010-07-09 17:58 ` Stefano Stabellini
2010-07-12 16:46 ` Ian Jackson
2010-07-11 22:14 ` Vincent Hanquez
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=4C37027A.5030207@eu.citrix.com \
--to=vincent.hanquez@eu.citrix.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=Tim.Deegan@eu.citrix.com \
--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.