From: George Dunlap <george.dunlap@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: george.dunlap@eu.citrix.com
Subject: [PATCH 0 of 2] libxc: Print domain ID with libxc save/restore messages
Date: Fri, 9 Mar 2012 17:29:36 +0000 [thread overview]
Message-ID: <patchbomb.1331314176@drall.uk.xensource.com> (raw)
XenServer implements logging functions to redirect libxc output to
syslog. Unfortunately, this means that when running a large number of
operations in parallel, the status messages from different save and
restore operations get mixed up, and it's hard to tell which is which.
This patch series adds code to print the domain ID in the messages of
all save-restore code.
Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com>
next reply other threads:[~2012-03-09 17:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 17:29 George Dunlap [this message]
2012-03-09 17:29 ` [PATCH 1 of 2] libxc: Pass the save_ctx struct to more functions George Dunlap
2012-03-13 16:15 ` Ian Jackson
2012-03-09 17:29 ` [PATCH 2 of 2] libxc: Print domain ID in save restore messages George Dunlap
2012-03-09 18:19 ` Ian Campbell
2012-03-09 18:25 ` George Dunlap
2012-03-09 18:33 ` Ian Campbell
2012-03-12 10:37 ` George Dunlap
2012-03-12 10:41 ` Ian Campbell
2012-03-13 16:15 ` 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=patchbomb.1331314176@drall.uk.xensource.com \
--to=george.dunlap@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).