From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH RFC v6.1 11-14/10] libxl: asynchronous operations
Date: Mon, 9 Jan 2012 17:34:33 +0000 [thread overview]
Message-ID: <1326130477-18085-1-git-send-email-ian.jackson@eu.citrix.com> (raw)
In-Reply-To: <1325882107-5794-1-git-send-email-ian.jackson@eu.citrix.com>
Here are four more patches to go onto the end of my previous 10-patch
event series posting:
11/10 libxl: Asynchronous/long-running operation infrastructure
12/10 libxl: New convenience macro CONTAINING_STRUCT
13/10 libxl: Introduce libxl__ev_devstate
14/10 libxl: Convert to asynchronous: device removal
This introduces a standard way for the same libxl function to be
useable both by simple-minded callers who want to wait synchronously,
and by advanced callers who want to the function to return immediately
and arrange a callback or event later.
next prev parent reply other threads:[~2012-01-09 17:34 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 20:34 [PATCH v6 00/10] libxl: event API Ian Jackson
2012-01-06 20:34 ` [PATCH 01/10] libxl: make LIBXL_INIT_GC a statement, not an initialiser Ian Jackson
2012-01-06 20:34 ` [PATCH 02/10] xenstore: New function xs_path_is_subpath Ian Jackson
2012-01-13 10:39 ` Ian Campbell
2012-01-06 20:35 ` [PATCH 03/10] libxl: move a lot more includes into libxl_internal.h Ian Jackson
2012-01-13 10:41 ` Ian Campbell
2012-01-13 13:37 ` Ian Jackson
2012-01-13 13:39 ` Ian Campbell
2012-01-13 16:23 ` Ian Jackson
2012-01-06 20:35 ` [PATCH 04/10] libxl: Provide more formal libxl__ctx_lock and _unlock Ian Jackson
2012-01-13 10:42 ` Ian Campbell
2012-01-06 20:35 ` [PATCH 05/10] libxl: Fix leaks on context init failure Ian Jackson
2012-01-13 10:43 ` Ian Campbell
2012-01-13 15:58 ` Ian Jackson
2012-01-06 20:35 ` [PATCH 06/10] DROP: libxl: rename libxl__free_all Ian Jackson
2012-01-06 20:35 ` [PATCH 07/10] libxl: New API for providing OS events to libxl Ian Jackson
2012-01-11 17:32 ` Stefano Stabellini
2012-01-12 11:28 ` Ian Campbell
2012-01-12 13:49 ` Stefano Stabellini
2012-01-12 15:49 ` Ian Jackson
2012-01-12 15:56 ` Ian Jackson
2012-01-13 15:07 ` Ian Campbell
2012-01-13 15:47 ` Ian Jackson
2012-01-13 15:56 ` Ian Campbell
2012-01-13 16:34 ` Ian Jackson
2012-01-06 20:35 ` [PATCH 08/10] libxl: New event generation API Ian Jackson
2012-01-13 15:22 ` Ian Campbell
2012-01-13 15:49 ` Ian Jackson
2012-01-06 20:35 ` [PATCH 09/10] libxl: introduce libxl_fd_set_nonblock, rationalise _cloexec Ian Jackson
2012-01-13 10:45 ` Ian Campbell
2012-01-13 15:54 ` Ian Jackson
2012-01-06 20:35 ` [PATCH 10/10] libxl: Permit multithreaded event waiting Ian Jackson
2012-01-09 17:34 ` Ian Jackson [this message]
2012-01-09 17:34 ` [PATCH 11/10] libxl: Asynchronous/long-running operation infrastructure Ian Jackson
2012-01-09 17:34 ` [PATCH 12/10] libxl: New convenience macro CONTAINING_STRUCT Ian Jackson
2012-01-13 10:49 ` Ian Campbell
2012-01-13 13:53 ` Ian Jackson
2012-01-13 15:06 ` Ian Campbell
2012-01-09 17:34 ` [PATCH 13/10] libxl: Introduce libxl__ev_devstate Ian Jackson
2012-01-09 17:34 ` [PATCH 14/10] libxl: Convert to asynchronous: device removal Ian Jackson
2012-01-13 14:50 ` [PATCH v6 00/10] libxl: event API Ian Campbell
2012-01-13 15:03 ` Ian Jackson
2012-01-13 17:43 ` Ian Jackson
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=1326130477-18085-1-git-send-email-ian.jackson@eu.citrix.com \
--to=ian.jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).