xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
* Xenformat to analyze eventmask
@ 2016-06-07  7:18 andrew pheony
  2016-06-07 10:28 ` Dario Faggioli
  0 siblings, 1 reply; 2+ messages in thread
From: andrew pheony @ 2016-06-07  7:18 UTC (permalink / raw)
  To: xen-devel


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

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
        using xenformat to analyze trace
        command:
        cat output.trace | /usr/local/bin/xentrace_format myformats
        myformats contents:
        0x0020f000  CPU%(cpu)d  %(tsc)d (+%(reltsc)8d)
        just want to print cpuid and timestamp for example but nothing
shows up
        what i am doing wrong?


Thanks
Andrew

[-- Attachment #1.2: Type: text/html, Size: 818 bytes --]

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

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Xenformat to analyze eventmask
  2016-06-07  7:18 Xenformat to analyze eventmask andrew pheony
@ 2016-06-07 10:28 ` Dario Faggioli
  0 siblings, 0 replies; 2+ messages in thread
From: Dario Faggioli @ 2016-06-07 10:28 UTC (permalink / raw)
  To: andrew pheony, xen-devel


[-- 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.

Regards,
Dario
-- 
<<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
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2016-06-07 10:28 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-06-07  7:18 Xenformat to analyze eventmask andrew pheony
2016-06-07 10:28 ` Dario Faggioli

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