xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Shriram Rajagopalan <rshriram@cs.ubc.ca>
To: xen-devel@lists.xen.org
Cc: Ian Jackson <ian.jackson@eu.citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH 0 of 2] libxl: AO support in domain suspend ops
Date: Sun, 24 Nov 2013 08:52:02 -0800	[thread overview]
Message-ID: <patchbomb.1385311922@athos.nss.cs.ubc.ca> (raw)

Make libxl's suspend callback be asynchronous and refactor the code
accordingly.  Ian J's patch on introducing the async suspend stub
functions has been merged into patch 2.

[1/2] Add an asynchronous version of the common suspend core
      (libxl__domain_suspend_common_callback), while retaining
      the existing synchronous version.  Add a callout to Remus
      (libxl__domain_suspend_callback_remus) that gets called post
      domain suspend.  Remus specific post-suspend tasks are
      implemented here.

[2/2] Remove the synchronous version of libxl__domain_suspend_common_callback.
      Also remove the separate entry point for Remus (libxl__remus_domain_suspend_callback).
      Instead, introduce a common entry point (libxl__domain_suspend_callback).

N.B. This series depends on the remus network buffering patch series.

thanks
shriram

             reply	other threads:[~2013-11-24 16:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-24 16:52 Shriram Rajagopalan [this message]
2013-11-24 16:52 ` [PATCH 1 of 2] libxl: async version of domain suspend Shriram Rajagopalan
2013-12-11  7:38   ` Dong, Eddie
2013-12-11 17:59   ` Shriram Rajagopalan
2013-12-12 15:08     ` Ian Jackson
2013-12-12 18:17       ` Shriram Rajagopalan
2013-12-12 18:34         ` Ian Jackson
2013-11-24 16:52 ` [PATCH 2 of 2] libxl: make libxl__domain_suspend_callback be asynchronous Shriram Rajagopalan

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=patchbomb.1385311922@athos.nss.cs.ubc.ca \
    --to=rshriram@cs.ubc.ca \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.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 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).