From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xen.org
Subject: libxl: events: debugging improvements
Date: Tue, 15 May 2012 15:09:55 +0100 [thread overview]
Message-ID: <1337090999-15608-1-git-send-email-ian.jackson@eu.citrix.com> (raw)
These four patches may help people who are working with the libxl
event machinery:
1/4 libxl: events: debugging output for timeouts
2/4 libxl: events: improve debugging output for xs watches
3/4 libxl: events: debugging output for fds
4/4 libxl: events: STATE_AO_GC checks ao is still valid
The first three are not intended to cause any change other than the
new debug messages. The last one should simply cause erroneous code
to crash sooner.
next reply other threads:[~2012-05-15 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 14:09 Ian Jackson [this message]
2012-05-15 14:09 ` [PATCH 1/4] libxl: events: debugging output for timeouts Ian Jackson
2012-05-15 14:09 ` [PATCH 2/4] libxl: events: improve debugging output for xs watches Ian Jackson
2012-05-15 14:09 ` [PATCH 3/4] libxl: events: debugging output for fds Ian Jackson
2012-05-15 14:09 ` [PATCH 4/4] libxl: events: STATE_AO_GC checks ao is still valid Ian Jackson
2012-05-17 13:46 ` libxl: events: debugging improvements Ian Campbell
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=1337090999-15608-1-git-send-email-ian.jackson@eu.citrix.com \
--to=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).