From: Dario Faggioli <dario.faggioli@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Paul Sujkov <psujkov@gmail.com>,
Ben Sanda <Ben.Sanda@dornerworks.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Julien Grall <julien.grall@arm.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
"stefano.stabellini" <stefano.stabellini@eu.citrix.com>
Subject: Re: Xentrace on Xilinx ARM
Date: Wed, 9 Mar 2016 12:22:22 +0100 [thread overview]
Message-ID: <1457522542.3102.341.camel@citrix.com> (raw)
In-Reply-To: <56DF1AD3.4050404@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1459 bytes --]
On Tue, 2016-03-08 at 18:32 +0000, Andrew Cooper wrote:
> On 08/03/16 18:28, Paul Sujkov wrote:
> > 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.
>
It sure should. However, I would not expect the ARM binary, built when
building of the tools for ARM, to work on an x86 box (either dom0,
devbox, or whatever). That's what I think Ben was asking about, and
what I was responding to.
> 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.
>
Apart from my recent enhancement in events displaying, I'm quite sure I
remember Coverity uncovering something pretty important about how some
stats were being handled, and that being fixed not more that a couple
of weeks ago.
Ah, here it is: ebdba150bff1d914805d60efa576337bbef0c305
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
next prev parent reply other threads:[~2016-03-09 11:22 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
2016-03-09 11:22 ` Dario Faggioli [this message]
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=1457522542.3102.341.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=Ben.Sanda@dornerworks.com \
--cc=andrew.cooper3@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).