From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xensource.com
Subject: Re: how to avoid lost trace records?
Date: Fri, 19 Nov 2010 22:30:41 +0100 [thread overview]
Message-ID: <20101119213041.GA16043@aepfle.de> (raw)
In-Reply-To: <20101119154652.GA11544@aepfle.de>
On Fri, Nov 19, Olaf Hering wrote:
> Today I inspected the xenalyze and the dump-raw output and noticed that
> huge number of lost trace records, even when booted with tbuf_size=200:
Adding some silly debug to insert_lost_records() to record the count of
the individual lost events shows lots of hypercall and stuff.
However, its odd that 20f101 gets past the 10f000 tb_event_mask in
__trace_var().
array index, cpu, event, number
(XEN) tb_control tb_event_mask 10f000
(XEN) trace.c:256:d0 tb_set_size from 239 to 20 not implemented
(XEN) insert_lost_records #0 c 2 e 20f101 n 7545b
(XEN) insert_lost_records #1 c 2 e 20f104 n 22de8
(XEN) insert_lost_records #2 c 2 e 21211 n 169e
(XEN) insert_lost_records #3 c 2 e 28004 n 16f2
(XEN) insert_lost_records #4 c 2 e 28006 n 183a
(XEN) insert_lost_records #5 c 2 e 2800e n 2fdb
(XEN) insert_lost_records #6 c 2 e 2800f n 2fdb
(XEN) insert_lost_records #7 c 2 e 2800a n 2fdb
(XEN) insert_lost_records #8 c 2 e 21021 n 17f2
(XEN) insert_lost_records #9 c 2 e 21101 n 2fdb
(XEN) insert_lost_records #10 c 2 e 21011 n 17df
(XEN) insert_lost_records #11 c 2 e 20f008 n ce
(XEN) insert_lost_records #12 c 2 e 20f103 n 717
(XEN) insert_lost_records #13 c 2 e 20f10b n 1145
(XEN) insert_lost_records #14 c 2 e 20f106 n 16f
(XEN) insert_lost_records #15 c 2 e 21002 n 97
(XEN) insert_lost_records #16 c 2 e 801001 n 5a
(XEN) insert_lost_records #17 c 2 e 802001 n 21b4
(XEN) insert_lost_records #18 c 2 e 802002 n 21b3
(XEN) insert_lost_records #19 c 2 e 21031 n a
(XEN) insert_lost_records #20 c 2 e 21311 n a
(XEN) insert_lost_records #21 c 2 e 1f004 n 1
(XEN) insert_lost_records #22 c 2 e 10f005 n 800
(XEN) insert_lost_records #23 c 2 e 10f03b n 800
(XEN) cpupool_add_domain(dom=1,pool=0) n_dom 2
(XEN) insert_lost_records #0 c 3 e 20f101 n 7c4df
(XEN) insert_lost_records #1 c 3 e 20f104 n 219b6
(XEN) insert_lost_records #2 c 3 e 20f103 n b28
(XEN) insert_lost_records #3 c 3 e 28006 n 1a31
(XEN) insert_lost_records #4 c 3 e 2800e n 33e2
(XEN) insert_lost_records #5 c 3 e 2800f n 33e2
(XEN) insert_lost_records #6 c 3 e 2800a n 33e2
(XEN) insert_lost_records #7 c 3 e 21021 n 19db
(XEN) insert_lost_records #8 c 3 e 21101 n 33e2
(XEN) insert_lost_records #9 c 3 e 802001 n 29db
(XEN) insert_lost_records #10 c 3 e 802002 n 29da
(XEN) insert_lost_records #11 c 3 e 21011 n 19f9
(XEN) insert_lost_records #12 c 3 e 21211 n 1b99
(XEN) insert_lost_records #13 c 3 e 28004 n 1de4
(XEN) insert_lost_records #14 c 3 e 20f008 n f3
(XEN) insert_lost_records #15 c 3 e 801001 n 53
(XEN) insert_lost_records #16 c 3 e 20f10b n 10d7
(XEN) insert_lost_records #17 c 3 e 21002 n ad
(XEN) insert_lost_records #18 c 3 e 21031 n e
(XEN) insert_lost_records #19 c 3 e 21311 n e
(XEN) insert_lost_records #20 c 3 e 20f106 n 28c
(XEN) insert_lost_records #21 c 3 e 1f004 n 529
(XEN) insert_lost_records #0 c 3 e 10f005 n 1c7a6
(XEN) insert_lost_records #1 c 3 e 10f03b n f1
(XEN) insert_lost_records #0 c 5 e 20f101 n 7134e
(XEN) insert_lost_records #1 c 5 e 20f104 n 23dc3
(XEN) insert_lost_records #2 c 5 e 20f103 n 62b
...
next prev parent reply other threads:[~2010-11-19 21:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 15:46 how to avoid lost trace records? Olaf Hering
2010-11-19 21:30 ` Olaf Hering [this message]
2010-11-20 20:21 ` Olaf Hering
2010-11-22 11:53 ` George Dunlap
2010-11-22 12:40 ` Olaf Hering
2010-11-22 12:51 ` George Dunlap
2010-11-22 13:46 ` Keir Fraser
2010-11-22 14:43 ` George Dunlap
2010-11-25 21:04 ` Olaf Hering
2010-11-25 22:27 ` Keir Fraser
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=20101119213041.GA16043@aepfle.de \
--to=olaf@aepfle.de \
--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.