Re: [Xen-devel] xentrace, xenalyze

[George Dunlap <george.dunlap@xxxxxxxxxx>]

On 24/02/16 13:21, Paul Sujkov wrote:
> 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.
> 
> 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:
> 
> 1. to understand how can I use xenalyze to find bottlenecks in the system
> at the moment
> 2. to add VGPU scheduler traces to Xen trace subsystem, xenbaked, xentrace
> and xenalyze
> 
> 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.

Thanks, Paul.

First of all: I'm not sure anyone has used xenbaked in ages; xentrace
itself is just a daemon to shovel data from the hypervisor into a file
-- it doesn't need to know anything about what's being traced (for the
most part).  That just leaves adding traces to the hypervisor,
xentrace_format, and xenalyze.

I think actually the first thing you might need to do is to get the
xentrace infrastructure working on ARM.  At least at some point there
was no way for dom0 to map the xentrace pages (but that may have changed).

After that, the next thing would be to add the equivalent of VMEXIT and
VMENTRY traces in the hypervisor on ARM guest exit and entry, and then
add support for analyzing that data to xenalyze.

Once you've got that done, then you just add in extra tracing
information as you need to drill down and figure out what's going on. :-)

 -George

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