From: Charles Duffy <cduffy@spamcop.net>
To: Ewan Mellor <ewan@xensource.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Timing out waiting for vbd device *only when xend started with trace_start*
Date: Mon, 14 Nov 2005 10:40:58 -0600 [thread overview]
Message-ID: <4378BE1A.6060901@spamcop.net> (raw)
In-Reply-To: <20051114163139.GH16045@leeni.uk.xensource.com>
Ewan Mellor wrote:
> On Mon, Nov 14, 2005 at 10:11:27AM -0600, Charles Duffy wrote:
>
>>It might be nice if the xend trace handler were expanded to print both
>>current PID (or thread name) and timestamp when indicating that a line
>>is being executed.
>
> Ask and ye shall receive an attachment.
Nifty -- but not quite what I had in mind.
I was thinking about modifying the *tracing*, not the *logging*; thus,
it would be the code in xend/server/SrvDaemon.py:trace that would be
impacted.
This would allow for a substantially higher granularity -- seeing where
we are not just on every log statement, but on every line executed by
the interpreter.
next prev parent reply other threads:[~2005-11-14 16:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dl67oi$cql$1@sea.gmane.org>
[not found] ` <dl768o$4r6$1@sea.gmane.org>
2005-11-13 17:37 ` Working hotplug, but still timing out waiting for vbd device ("changing physical-device not supported"?) Charles Duffy
2005-11-14 0:59 ` [FIXED] Re: Working hotplug, but still timing out waiting for vbd device Charles Duffy
2005-11-14 1:21 ` [FIXED - NOT!] " Charles Duffy
2005-11-14 11:31 ` Timing out waiting for vbd device *only when xend started with trace_start* Charles Duffy
2005-11-14 11:51 ` Ewan Mellor
2005-11-14 12:43 ` Charles Duffy
[not found] ` <43789319.9090609@spamcop.net>
[not found] ` <20051114151038.GB16045@leeni.uk.xensource.com>
2005-11-14 16:11 ` Charles Duffy
2005-11-14 16:31 ` Ewan Mellor
2005-11-14 16:40 ` Charles Duffy [this message]
2005-11-14 17:20 ` Ewan Mellor
2005-11-15 15:20 ` Ewan Mellor
2005-11-14 11:58 ` Working hotplug, but still timing out waiting for vbd device ("changing physical-device not supported"?) Ewan Mellor
2005-11-14 12:10 ` Charles Duffy
2005-11-14 12:27 ` Ewan Mellor
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=4378BE1A.6060901@spamcop.net \
--to=cduffy@spamcop.net \
--cc=ewan@xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.