From: Rob Gardner <rob.gardner@hp.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-tools@lists.xensource.com, xen-devel@lists.xensource.com,
rickey berkeley <rickey.berkeley@gmail.com>,
NAHieu <nahieu@gmail.com>,
ryanh@us.ibm.com, xen-users@lists.xensource.com
Subject: Re: Hi,something about the xentrace tool
Date: Thu, 15 Jun 2006 10:41:29 -0600 [thread overview]
Message-ID: <44918DB9.2010105@hp.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D4BAAAA@liverpoolst.ad.cl.cam.ac.uk>
[-- Attachment #1.1: Type: text/plain, Size: 352 bytes --]
Ian Pratt wrote:
>> If overflow occurs, it is not handled. The mechanism I implemented was
>> just designed to drastically reduce the probability of overflow.
>>
>
> It does count the number of lost trace messages and add a trace message
> to that effect though, right?
>
No, but I'll add that to the list of things to do in the future.
Rob
[-- Attachment #1.2: Type: text/html, Size: 784 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-06-15 16:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 7:06 Hi,something about the xentrace tool Ian Pratt
2006-06-15 8:58 ` [Xen-devel] " rickey berkeley
2006-06-15 17:03 ` Rob Gardner
2006-06-15 18:20 ` George Dunlap
2006-06-15 18:28 ` George Dunlap
2006-06-15 18:53 ` Rob Gardner
2006-06-19 1:06 ` George Dunlap
2006-06-19 5:00 ` Rob Gardner
2006-06-19 14:02 ` George Dunlap
2006-06-19 17:19 ` Rob Gardner
2006-06-21 19:02 ` George Dunlap
2006-06-15 16:41 ` Rob Gardner [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-19 7:14 Ian Pratt
2006-06-16 14:11 Ian Pratt
2006-06-16 16:56 ` Rob Gardner
2006-06-11 13:17 rickey berkeley
2006-06-12 15:17 ` George Dunlap
2006-06-12 15:30 ` Ryan Harper
2006-06-13 17:11 ` rickey berkeley
2006-06-13 17:25 ` Rob Gardner
2006-06-14 3:47 ` NAHieu
2006-06-14 16:06 ` Rob Gardner
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=44918DB9.2010105@hp.com \
--to=rob.gardner@hp.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=nahieu@gmail.com \
--cc=rickey.berkeley@gmail.com \
--cc=ryanh@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-tools@lists.xensource.com \
--cc=xen-users@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.