From: Jennifer Herbert <Jennifer.Herbert@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xenproject.org,
Ian Jackson <ian.jackson@eu.citrix.com>,
jtotto@uwaterloo.ca
Subject: Re: [PATCH v3 3/3] RFC: migration: defer precopy policy to libxl
Date: Tue, 26 Sep 2017 10:42:49 +0100 [thread overview]
Message-ID: <59CA2119.1090200@citrix.com> (raw)
In-Reply-To: <20170926084819.yrzz4ki2urh4lt5d@citrix.com>
On 26/09/17 09:48, Wei Liu wrote:
> On Mon, Sep 25, 2017 at 07:55:35PM +0100, Jennifer Herbert wrote:
>> Provide an implementation of the old policy as a callback in
>> libxl and plumb it through the IPC machinery to libxc.
>>
>> This serves as an example for defining a libxl policy,
>> and provides no advantage over the default policy in libxc.
>>
>> Signed-off-by: Joshua Otto <jtotto@uwaterloo.ca>
>> Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>
> The code looks plausible but it is not really usable by libxl users
> as-is, because a public API is still missing.
This is why I excluded it to start with, and now labelled it RFC.
Its only the first two patches I would like to see pulled atm.
Cheers
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-09-26 9:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 18:55 [PATCH v3 0/3] Introduce migration precopy policy Jennifer Herbert
2017-09-25 18:55 ` [PATCH v3 1/3] Tidy libxc xc_domain_save Jennifer Herbert
2017-09-25 18:55 ` [PATCH v3 2/3] Introduce migration precopy policy Jennifer Herbert
2017-09-26 8:36 ` Wei Liu
2017-09-26 10:58 ` Andrew Cooper
2017-09-26 11:38 ` Jennifer Herbert
2017-09-26 11:02 ` Andrew Cooper
2017-09-26 11:49 ` Jennifer Herbert
2017-09-25 18:55 ` [PATCH v3 3/3] RFC: migration: defer precopy policy to libxl Jennifer Herbert
2017-09-26 8:48 ` Wei Liu
2017-09-26 9:42 ` Jennifer Herbert [this message]
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=59CA2119.1090200@citrix.com \
--to=jennifer.herbert@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jtotto@uwaterloo.ca \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).