From: Andrew Cooper <andrew.cooper3@citrix.com>
To: hanyandong <hanyandong@iie.ac.cn>, xen-devel@lists.xen.org
Subject: Re: About lost record of xentrace, how to avoid lost record?
Date: Wed, 26 Nov 2014 10:53:43 +0000 [thread overview]
Message-ID: <5475B137.6010405@citrix.com> (raw)
In-Reply-To: <1dba4f1.45dd7.149eafa167d.Coremail.hanyandong@iie.ac.cn>
[-- Attachment #1.1: Type: text/plain, Size: 481 bytes --]
On 26/11/14 07:21, hanyandong wrote:
> hi all,
> I found xentrace will lost record if there are too many event to trace.
> But every event is important to me, so I want to trace all of them,
> not lost one.
> what could I do to achieve this goal ?
>
> If it need to modify the source code of xentrace, I will do it. But
> will anyone give me some instructions?
xentrace --trace-buf-size=$NUM where $NUM defaults to 32. Try making it
larger and see whether that helps.
~Andrew
[-- Attachment #1.2: Type: text/html, Size: 1044 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-11-26 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 7:21 About lost record of xentrace, how to avoid lost record? hanyandong
2014-11-26 10:53 ` Andrew Cooper [this message]
2014-12-01 11:27 ` George Dunlap
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=5475B137.6010405@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=hanyandong@iie.ac.cn \
--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 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.