xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: andrew pheony <igiveitashot@gmail.com>, xen-devel@lists.xen.org
Subject: Re: Xenformat to analyze eventmask
Date: Tue, 7 Jun 2016 12:28:35 +0200	[thread overview]
Message-ID: <1465295315.15816.78.camel@citrix.com> (raw)
In-Reply-To: <CAFV2zDQmbPyq4UYc4ZY=sQKWqKCLDQvELN0iyTWf6tbHHVn5wA@mail.gmail.com>

[-- Attachment #1.1: Type: text/plain, Size: 1084 bytes --]

On Tue, 2016-06-07 at 12:48 +0530, andrew pheony wrote:
> Hello experts,
>         I tried collecting trace of pv guest vm on xen 4.6.1 with
> xentrace.
>         Command used for capturing trace:  /usr/local/sbin/xentrace
> -D -e 0x0020f000 output.trace
What kind of events are you trying to capture and then analyze?

Is it possible that what you want would be something like this:

 xentrace -D -e 0x2f000 output.trace

(note the difference between your 0x20f000 and my 0x2f000)

>         using xenformat to analyze trace
>         command:        
>         cat output.trace | /usr/local/bin/xentrace_format myformats
This part looks ok.

Once you've got the event selection right, I'd suggest you to have a
look at xenalyze as well.

<<This happens because I choose it to happen!>> (Raistlin Majere)
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

Xen-devel mailing list

      reply	other threads:[~2016-06-07 10:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07  7:18 Xenformat to analyze eventmask andrew pheony
2016-06-07 10:28 ` Dario Faggioli [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1465295315.15816.78.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=igiveitashot@gmail.com \
    --cc=xen-devel@lists.xen.org \


* 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).