From: Olaf Hering <olaf@aepfle.de>
To: George Dunlap <dunlapg@umich.edu>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: how to avoid lost trace records?
Date: Mon, 22 Nov 2010 13:40:15 +0100 [thread overview]
Message-ID: <20101122124014.GA1837@aepfle.de> (raw)
In-Reply-To: <AANLkTinprmdxM3EWN_59hEVc5fp0xNdh2XmDwUypimLR@mail.gmail.com>
On Mon, Nov 22, George Dunlap wrote:
> Olaf,
>
> Dang, 8 megs per cpu -- but I guess that's really not so much overhead
> on a big machine; and it's definitely worth getting around the lost
> records issue. Send the T_INFO_PAGES patch to the list, and see what
> Keir thinks.
Yes, will do.
Sometimes there is a boost of records, like set_p2m_entry and the like.
They all happen on the same cpu, so the per_cpu buffer fills up quickly.
And thats what I'm debugging right now. Too bad, tracing adds overhead
so the bug disappears. So, back to reading source code and find the race
that way.
Olaf
next prev parent reply other threads:[~2010-11-22 12:40 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
2010-11-20 20:21 ` Olaf Hering
2010-11-22 11:53 ` George Dunlap
2010-11-22 12:40 ` Olaf Hering [this message]
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=20101122124014.GA1837@aepfle.de \
--to=olaf@aepfle.de \
--cc=dunlapg@umich.edu \
--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).