From: Jennifer Herbert <Jennifer.Herbert@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org, Wei Liu <wei.liu2@citrix.com>,
jtotto@uwaterloo.ca
Subject: Re: [PATCH 2/2] Introduce migration precopy policy
Date: Mon, 18 Sep 2017 15:46:30 +0100 [thread overview]
Message-ID: <59BFDC46.2010507@citrix.com> (raw)
In-Reply-To: <22975.51802.455710.12987@mariner.uk.xensource.com>
On 18/09/17 14:30, Ian Jackson wrote:
> Jennifer Herbert writes ("[PATCH 2/2] Introduce migration precopy policy"):
>> This Patch allows a migration precopy policy to be specified.
> But only for direct libxc users. How do you think this should be
> exposed via libxl ?
The original patch had a small amount of code to pass this though such
that libxl could provide one. I'm not entity sure how the perl code
worked, but I've not made any changes that wouldn't stop this working.
That section would form a follow on patch. Since I don't use or have
much understanding of libxl, I didn't really feel I was the best person
to do this.
-jenny
> The general approach, so far, seems sound.
>
> Thanks,
> Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-09-18 14:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 15:33 [PATCH 0/2] Introduce migration precopy policy Jennifer Herbert
2017-09-14 15:33 ` [PATCH 1/2] Tidy libxc xc_domain_save Jennifer Herbert
2017-09-18 8:46 ` Paul Durrant
2017-09-14 15:33 ` [PATCH 2/2] Introduce migration precopy policy Jennifer Herbert
2017-09-18 9:05 ` Paul Durrant
2017-09-18 13:20 ` Wei Liu
2017-09-18 13:21 ` Paul Durrant
2017-09-18 13:30 ` Ian Jackson
2017-09-18 14:46 ` Jennifer Herbert [this message]
2017-09-18 15:43 ` Ian Jackson
2017-09-18 13:49 ` Wei Liu
2017-09-14 15:33 ` [PATCH 0/2] " Jennifer Herbert
2017-09-14 15:34 ` [PATCH 1/2] Tidy libxc xc_domain_save Jennifer Herbert
2017-09-14 15:59 ` Wei Liu
2017-09-14 15:34 ` [PATCH 2/2] Introduce migration precopy policy Jennifer Herbert
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=59BFDC46.2010507@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).