xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Ben Sanda <Ben.Sanda@dornerworks.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: Paul Sujkov <psujkov@gmail.com>,
	George Dunlap <george.dunlap@eu.citrix.com>,
	Julien Grall <julien.grall@arm.com>,
	"stefano.stabellini" <stefano.stabellini@eu.citrix.com>
Subject: Re: Xentrace on Xilinx ARM
Date: Tue, 8 Mar 2016 13:41:58 +0100	[thread overview]
Message-ID: <1457440918.3102.193.camel@citrix.com> (raw)
In-Reply-To: <A2A949C387F3A54C9B4DAC2DCD2E9A85C38D539A@Quimby.dw.local>


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

[Adding (back?) George, which wrote and maintains xenalyze, and tracing
in general, and adding ARM people as well, because this is on ARM,
isn't it?]

On Mon, 2016-03-07 at 19:36 +0000, Ben Sanda wrote:
> it was in a mercurial repo here:  
> http://xenbits.xensource.com/ext/xenalyze.hg 
> 
> but that repo is no longer functional it seems. I searched through
> the mailing
> lists and it looks like xenalyze was pulled into the mainline and now
> resides in
> tools/xentrace. 
>
That's correct, it's all in tree now.

> I can't determine how to get it to build though. I've tried
> calling make in the directory but that fails. I'm using petalinux
> which has a
> build xen tools make object, which I have also tried, and it
> generates an object
> file for xenalyze.c, but no executable. 
>
Mmm... In an x86 build, this is what I get:
(debian-stable_amd64)dario@Solace:/home/SOURCES/xen/xen/xen.git$ ls tools/xentrace/xenalyze -lah
-rwxrwxr-x. 1 dario dario 174K Mar  8 12:36 tools/xentrace/xenalyze
(debian-stable_amd64)dario@Solace:/home/SOURCES/xen/xen/xen.git$ ls dist/install/usr/local/bin/xenalyze -lah
-rwxr-xr-x. 1 dario dario 174K Mar  8 12:36 dist/install/usr/local/bin/xenalyze

I guess we're talking about ARM (cross?) builds, which is something
(especially for tools!) that I really have not much experience with.

Maybe there's more to modify, in terms of Makefile-s, etc., to make
that be build on ARM...

> Could you provide any guidance as to how
> to actually get xenalyze built? I'm assuming it's still an offline
> tool? Or is it now
> built into the Xen image?
> 
It's not part of any Xen image. It's a command line tool to be used,
usually but not necessarily, in dom0, build and installed together with
the other tools... At least in my case, for x86 builds and installs.

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-03-08 12:41 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 [this message]
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
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=1457440918.3102.193.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=Ben.Sanda@dornerworks.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).