xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Paul Sujkov <psujkov@gmail.com>, xen-devel@lists.xen.org
Cc: george.dunlap@citrix.com
Subject: Re: xentrace, xenalyze
Date: Wed, 24 Feb 2016 15:51:59 +0100	[thread overview]
Message-ID: <1456325519.17312.70.camel@citrix.com> (raw)
In-Reply-To: <CA+KUHvyH57Ab7c=Hk-vQd2ANrgGnNnLef=c43D==w2QL48s2Gw@mail.gmail.com>


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

On Wed, 2016-02-24 at 15:21 +0200, Paul Sujkov wrote:
> Hi,
> 
Hi,

> I'm from GlobalLogic team that uses Xen as a base for an automative
> platform. Got few questions regarding Xen tracing and it seems that
> existing documentation is rather limited.
> 
It is...

> At the previous Xen Hackathon I was talking about shared (mediated
> pass-through) GPU concept for ARM; it's working well, but still has
> performance issues, and some of them seem to be correlated to other
> Xen subsystems, but it's not obvious why so (e.g. turning off pv real
> time clock driver gives us a significant boost in overall graphics
> performance). So, I'm looking for two things here actually:
> 
Great to hear you're (still) working on this. I'm looking forward to
see the results! :-D

> 1. to understand how can I use xenalyze to find bottlenecks in the
> system at the moment
>
This is hard to tell (at least with such a broad scope).

xentrace supports quite a bit of events, but enabling all of them may
may not be what you want. For one, it would produce traces that are so
big and complex to analyze, that it would be very hard to make sense
out of them.

I usually enable a subset of them (one or more "classes") and try to
figure out if I see the problem in the resulting trace. If yes, I try
with a narrower subset. If not, I try with either a broader or a
different one.

> 2. to add VGPU scheduler traces to Xen trace subsystem, xenbaked,
> xentrace and xenalyze
> 
I've never used xenbaked. I've only used xentrace_format and xenalyze.
I don't know if xenbaked still works/can still be useful.

> Some insights into the second question can be found in RTDS scheduler
> patches (it adds a few of it's own trace events and uses generic
> scheduler tracing); however, it uses already functioning scheduler
> tracing subsystem which is VCPU specific and is not suitable for
> VGPU, and there are no visible patches to xenalyze to parse these
> traces out.
> 
Have a look at this series:
 http://lists.xenproject.org/archives/html/xen-devel/2016-02/msg02233.html

And I've got another one that I'll send out asap (and I can Cc you).

There are for sure some examples of adding trace points in Xen, and
adding support for them in xentrace_format and xenalyze.

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: 181 bytes --]

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

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

  parent reply	other threads:[~2016-02-24 14:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24 13:21 xentrace, xenalyze Paul Sujkov
2016-02-24 14:41 ` George Dunlap
2016-02-24 15:24   ` Paul Sujkov
2016-02-24 15:53     ` Dario Faggioli
2016-02-24 15:58     ` George Dunlap
2016-02-24 17:58       ` Paul Sujkov
2016-02-24 14:51 ` Dario Faggioli [this message]
2016-02-24 16:00   ` Paul Sujkov
2016-02-24 16:19     ` George Dunlap

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=1456325519.17312.70.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=psujkov@gmail.com \
    --cc=xen-devel@lists.xen.org \
    /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).