All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v4] tools: set migration constraints from cmdline
Date: Tue, 5 Feb 2013 11:16:54 +0100	[thread overview]
Message-ID: <20130205101654.GA13955@aepfle.de> (raw)
In-Reply-To: <1360056173.7743.81.camel@zakaz.uk.xensource.com>

On Tue, Feb 05, Ian Campbell wrote:

> On Mon, 2013-02-04 at 18:43 +0000, Olaf Hering wrote:
> > On Mon, Feb 04, Ian Campbell wrote:
> > 
> > > It just occurred to me, instead of adding lots of individual arguments
> > > perhaps packing them into a (e.g.) libxl_save_properties and adding a
> > > pointer would be a nicer and more extensible (in the future) interface?
> > 
> > Something like this (copy&paste from hg diff)?
> 
> It's a tricky balance of what goes in the struct and what goes in the
> prototype but I didn't imagine putting domid or fd into the struct,
> domid because that's how other libxl APIs behave and fd because it isn't
> really a property of the save/migrate as such.
> 
> Moving flags into the struct could be optional is it complicates the
> compat code too much.

I sent v5 with a new libxl_domain_suspend prototype. If that direction
is ok I will look how to improve the LIBXL_API_VERSION handling and how
to provide a knob for DEF_MIN_REMAINING.

While I do that I would like to drop the hvm parameter from
xc_domain_save because there is a flag for this.

Olaf

  reply	other threads:[~2013-02-05 10:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28 17:32 [PATCH] tools: set migration constraints from cmdline Olaf Hering
2013-01-30 14:30 ` Ian Campbell
2013-01-30 16:43   ` Olaf Hering
2013-02-04  9:57   ` Olaf Hering
2013-02-04 12:54     ` Ian Campbell
2013-02-04 13:09       ` Olaf Hering
2013-02-04 13:14         ` Ian Campbell
2013-01-30 16:41 ` [PATCH v2] " Olaf Hering
2013-01-31 16:17 ` [PATCH v3] " Olaf Hering
2013-02-01 19:34 ` [PATCH v4] " Olaf Hering
2013-02-04 13:11   ` Ian Campbell
2013-02-04 13:41     ` Olaf Hering
2013-02-04 13:46       ` Ian Campbell
2013-02-04 13:55         ` Olaf Hering
2013-02-04 13:59           ` Ian Campbell
2013-02-04 18:43             ` Olaf Hering
2013-02-05  9:22               ` Ian Campbell
2013-02-05 10:16                 ` Olaf Hering [this message]
2013-02-19 11:42     ` Olaf Hering
2013-02-19 11:48       ` Ian Campbell
2013-02-19 14:12         ` Olaf Hering
2013-02-05 10:03 ` [PATCH v5] " Olaf Hering

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=20130205101654.GA13955@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=Ian.Campbell@citrix.com \
    --cc=xen-devel@lists.xen.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 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.