From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Simon Beaumont <simon.beaumont@citrix.com>
Cc: "xs-devel@lists.xenserver.org" <xs-devel@lists.xenserver.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: FW: Cancelling asynchronous operations in libxl
Date: Wed, 23 Oct 2013 13:23:29 -0400 [thread overview]
Message-ID: <20131023172329.GE28413@phenom.dumpdata.com> (raw)
In-Reply-To: <4B8F5D33B081C044AA43634E84ED7F9616A83D@AMSPEX01CL03.citrite.net>
On Tue, Oct 15, 2013 at 04:08:31PM +0000, Simon Beaumont wrote:
> We're in the process of porting xenopsd[1] to libxl, rather than driving libxc manually.
>
> Using our libxc-based backend, we are able to cancel operations. For operations that are using XenStore watches we wrap these in a cancellable_watch[2], and for operations that make use of a subprocess we send SIGKILL when we wish to cancel the associated task. We would then instrument any necessary cleanup by hand on a best-effort basis.
>
> With the move to libxl, a lot of this control will be abstracted away and it is unclear how best to allow long-running tasks to be cancelled. It seems most of these operations could be executed asynchronously but we wonder if it is possible to cancel them, or how we could add cancellation functionality to these operations?
Are there specific operations that you are focusing on to cancel?
Or is this mostly of 'the guest is doing something and does not seem
to have a vnc/console, lets kill it' ?
>
> Cheers,
>
> Si
>
> [1]: https://github.com/xapi-project/xenopsd
> [2]: https://github.com/xapi-project/xenopsd/blob/master/xc/cancel_utils.ml#L101
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next parent reply other threads:[~2013-10-23 17:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B8F5D33B081C044AA43634E84ED7F9616A83D@AMSPEX01CL03.citrite.net>
2013-10-23 17:23 ` Konrad Rzeszutek Wilk [this message]
2013-10-26 8:33 ` FW: Cancelling asynchronous operations in libxl Ian Campbell
[not found] ` <1382776392.22417.179.camel@hastur.hellion.org.uk>
2013-10-28 9:38 ` Simon Beaumont
2013-10-28 15:52 ` Ian Jackson
2013-10-31 13:52 ` Ian Campbell
2013-10-31 14:32 ` Ian Jackson
2013-10-31 17:09 ` Ian Campbell
2013-11-08 18:38 ` Ian Jackson
2013-11-20 11:01 ` Ian Campbell
2013-12-20 18:24 ` Ian Jackson
2013-12-20 18:45 ` [RFC PATCH 00/14] libxl: Asynchronous event cancellation Ian Jackson
2013-12-20 18:45 ` [PATCH 01/14] libxl: suspend: switch_logdirty_done takes rc Ian Jackson
2013-12-20 18:45 ` [PATCH 02/14] libxl: suspend: common suspend callbacks take rc Ian Jackson
2013-12-20 18:45 ` [PATCH 03/14] libxl: suspend: Return correct error from callbacks Ian Jackson
2013-12-20 18:45 ` [PATCH 04/14] libxl: Use libxl__xswait* in libxl__ao_device Ian Jackson
2013-12-20 18:45 ` [PATCH 05/14] libxl: xswait/devstate: Move xswait to before devstate Ian Jackson
2013-12-20 18:45 ` [PATCH 06/14] libxl: devstate: Use libxl__xswait* Ian Jackson
2013-12-20 18:45 ` [PATCH 07/14] libxl: New error codes CANCELLED etc Ian Jackson
2013-12-20 18:45 ` [PATCH 08/14] libxl: events: Permit timeouts to signal cancellation Ian Jackson
2013-12-20 18:45 ` [PATCH 09/14] libxl: domain create: Do not destroy on cancellation Ian Jackson
2013-12-20 18:45 ` [PATCH 10/14] libxl: ao: Record ultimate parent of a nested ao Ian Jackson
2013-12-20 18:45 ` [PATCH 11/14] libxl: ao: Count the nested progeny of an ao Ian Jackson
2013-12-20 18:45 ` [PATCH 12/14] libxl: ao: Provide manip_refcnt Ian Jackson
2013-12-20 18:45 ` [PATCH 13/14] libxl: ao: Cancellation API Ian Jackson
2013-12-20 18:45 ` [PATCH 14/14] libxl: ao: Timeouts are cancellable Ian Jackson
2014-03-14 10:42 ` FW: Cancelling asynchronous operations in libxl Ian Campbell
2014-03-14 12:32 ` Simon Beaumont
2014-03-14 17:09 ` Ian Jackson
2013-10-15 16:08 Simon Beaumont
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=20131023172329.GE28413@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=simon.beaumont@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=xs-devel@lists.xenserver.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).