From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Paul Sujkov <psujkov@gmail.com>, Ben Sanda <Ben.Sanda@dornerworks.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Dario Faggioli <dario.faggioli@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Julien Grall <julien.grall@arm.com>,
"stefano.stabellini" <stefano.stabellini@eu.citrix.com>
Subject: Re: Xentrace on Xilinx ARM
Date: Tue, 8 Mar 2016 18:32:51 +0000 [thread overview]
Message-ID: <56DF1AD3.4050404@citrix.com> (raw)
In-Reply-To: <CA+KUHvyS1FJp8nCJA=DZuuoqWOhGuBdvV+TeS1wfa6A=ojLJvQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 772 bytes --]
On 08/03/16 18:28, Paul Sujkov wrote:
> Hi Ben,
>
> looks like you've done everything I did. I'm far from my working
> laptop today, so I can post my work on this issue only tomorrow so you
> can look through the code, compare and estimate solutions.
>
> Regarding ARM build, I'm using xenalyze as both host tool (x86 build,
> e.g. for gnuplot scatterplot graphs) and target tool (ARM, for fast
> summary check); but since we're working with Xen 4.5, I'm building it
> outside Xen source tree with a custom Makefile.
xenalyse should be able to be run as a separate tool, and on a different
architecture. All it does is annotate the binary trace file.
I don't think there is much change between what's now in-tree and what
was out of tree in the 4.5 timeframe.
~Andrew
[-- Attachment #1.2: Type: text/html, Size: 1561 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-03-08 18:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 20:53 Xentrace on Xilinx ARM Ben Sanda
2016-03-05 15:43 ` Dario Faggioli
2016-03-07 3:20 ` Ben Sanda
2016-03-07 19:36 ` Ben Sanda
2016-03-07 20:30 ` Paul Sujkov
2016-03-07 20:32 ` Ben Sanda
2016-03-08 12:41 ` Dario Faggioli
2016-03-08 18:04 ` Ben Sanda
2016-03-08 18:15 ` Dario Faggioli
2016-03-08 18:28 ` Paul Sujkov
2016-03-08 18:32 ` Andrew Cooper [this message]
2016-03-09 11:22 ` Dario Faggioli
2016-03-08 18:44 ` George Dunlap
2016-03-08 20:51 ` Ben Sanda
2016-03-09 11:05 ` George Dunlap
2016-03-09 16:28 ` Ben Sanda
2016-03-09 11:41 ` Paul Sujkov
2016-03-09 16:26 ` Ben Sanda
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=56DF1AD3.4050404@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ben.Sanda@dornerworks.com \
--cc=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=julien.grall@arm.com \
--cc=psujkov@gmail.com \
--cc=stefano.stabellini@eu.citrix.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).