From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dario Faggioli Subject: Re: Xentrace on Xilinx ARM Date: Wed, 9 Mar 2016 12:22:22 +0100 Message-ID: <1457522542.3102.341.camel@citrix.com> References: <1457192589.2959.603.camel@citrix.com> <1457440918.3102.193.camel@citrix.com> <56DF1AD3.4050404@citrix.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7164376400464163685==" Return-path: In-Reply-To: <56DF1AD3.4050404@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Andrew Cooper , Paul Sujkov , Ben Sanda Cc: George Dunlap , Julien Grall , "xen-devel@lists.xen.org" , "stefano.stabellini" List-Id: xen-devel@lists.xenproject.org --===============7164376400464163685== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Blv4I6GBGixvSOn33ygQ" --=-Blv4I6GBGixvSOn33ygQ Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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. > =C2=A0 > xenalyse should be able to be run as a separate tool, and on a > different architecture.=C2=A0 All it does is annotate the binary trace > file. >=20 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. >=20 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:=C2=A0ebdba150bff1d914805d60efa576337bbef0c305 Regards, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-Blv4I6GBGixvSOn33ygQ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEABECAAYFAlbgB24ACgkQk4XaBE3IOsT8hgCfYizdjf7hNDtTuDmG5mvyuRSR dvUAoKBpHK1yvyO5GyCzN/tVMLyCJLzq =NKL1 -----END PGP SIGNATURE----- --=-Blv4I6GBGixvSOn33ygQ-- --===============7164376400464163685== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9y Zy94ZW4tZGV2ZWwK --===============7164376400464163685==--