All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Gardner <rob.gardner@hp.com>
To: rickey berkeley <rickey.berkeley@gmail.com>
Cc: xen-tools@lists.xensource.com, ryanh@us.ibm.com,
	xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: Hi,something about the xentrace tool
Date: Tue, 13 Jun 2006 11:25:20 -0600	[thread overview]
Message-ID: <448EF500.7070506@hp.com> (raw)
In-Reply-To: <8061f8830606131011w732d1501x6fb81c37e1239553@mail.gmail.com>

rickey berkeley wrote:
> Based on trace source code(xen/common/trace.c),dom0 tracing the event 
> which are enabled.
>
> xen initialize tracing buffer for each cpu,trace buffer size (in 
> pages) in kenel space is defined by opt_tbuf_size.
> The tracing buf use loop structure.
>
> I guess when the tracing data increase rapidly ,and xentrace tool in 
> user space does not take them immediately.
> Some tracing data will lost.Maybe relayfs or something else can solve 
> this problem.
>

I added a basic flow control mechanism to the trace buffer system a few 
months ago. You can see an example of how to use it in tools/xenmon. The 
way it works is that as trace records are generated, a software 
interrupt is generated when the trace buffer gets filled to a certain 
point. The user space tools can use select() on an event channel to find 
out about these interrupts. See tools/xenmon/xenbaked.c for exact 
programming details. This code has not been copied into xentrace yet; 
Feel free to do so yourself if you think it's necessary.

Rob

  reply	other threads:[~2006-06-13 17:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-11 13:17 Hi,something about the xentrace tool 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 [this message]
2006-06-14  3:47       ` NAHieu
2006-06-14 16:06         ` Rob Gardner
  -- strict thread matches above, loose matches on Subject: below --
2006-06-15  7:06 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
2006-06-16 14:11 Ian Pratt
2006-06-16 16:56 ` Rob Gardner
2006-06-19  7:14 Ian Pratt

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=448EF500.7070506@hp.com \
    --to=rob.gardner@hp.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.