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: Mon, 4 Feb 2013 19:43:02 +0100	[thread overview]
Message-ID: <20130204184301.GA31487@aepfle.de> (raw)
In-Reply-To: <1359986349.7743.46.camel@zakaz.uk.xensource.com>

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)?
I did not find a way to put also libxl_asyncop_how into
libxl_save_properties, the checker complains about missing
LIBXL_EXTERNAL_CALLERS_ONLY.

Olaf

diff -r 6087ff7a1aea tools/libxl/libxl.h
--- a/tools/libxl/libxl.h
+++ b/tools/libxl/libxl.h
@@ -500,18 +500,24 @@ int libxl_domain_create_restore(libxl_ct
 void libxl_domain_config_init(libxl_domain_config *d_config);
 void libxl_domain_config_dispose(libxl_domain_config *d_config);

+typedef struct {
+    uint32_t domid;
+    int fd;
+    int flags; /* LIBXL_SUSPEND_* */
+    int max_iters;
+    int max_factor;
+} libxl_save_properties;
+
 int libxl_domain_suspend_0x040200(libxl_ctx *ctx, uint32_t domid, int fd,
-                         int flags, /* LIBXL_SUSPEND_* */
-                         const libxl_asyncop_how *ao_how)
-                         LIBXL_EXTERNAL_CALLERS_ONLY;
+                                  int flags, /* LIBXL_SUSPEND_* */
+                                  const libxl_asyncop_how *ao_how)
+                                  LIBXL_EXTERNAL_CALLERS_ONLY;
 #ifdef LIBXL_API_VERSION
 #if LIBXL_API_VERSION == 0x040200
 #define libxl_domain_suspend libxl_domain_suspend_0x040200
 #endif
 #else
-int libxl_domain_suspend(libxl_ctx *ctx, uint32_t domid, int fd,
-                         int flags, /* LIBXL_SUSPEND_* */
-                         int max_iters, int max_factor,
+int libxl_domain_suspend(libxl_ctx *ctx, const libxl_save_properties *props,
                          const libxl_asyncop_how *ao_how)
                          LIBXL_EXTERNAL_CALLERS_ONLY;
 #endif

  reply	other threads:[~2013-02-04 18:43 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 [this message]
2013-02-05  9:22               ` Ian Campbell
2013-02-05 10:16                 ` Olaf Hering
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=20130204184301.GA31487@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.