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 19:15:02 +0100 [thread overview]
Message-ID: <1457460902.3102.282.camel@citrix.com> (raw)
In-Reply-To: <A2A949C387F3A54C9B4DAC2DCD2E9A85C38D53E7@Quimby.dw.local>
[-- Attachment #1.1: Type: text/plain, Size: 2598 bytes --]
On Tue, 2016-03-08 at 18:04 +0000, Ben Sanda wrote:
> All,
>
> To update to the current situation. I have been able to get
> xentrace() and
> xenalyze working completely (at least as far as I can tell) on ARM.
>
Great! :-)
> For xentrace there were changes to the memory allocation routines to
> allow
> mapping of the Xen Heap by dom0, correcting the MFN->PFN
> translations, adding
> the trace buffer initialization to setup.c (init_trace_bufs), and
> correcting the
> get_cycles() call to provide the system TSC. For the get_cycles()
> call I
> gathered that was supposed to return the raw tick count, not a
> translated
> ticks->real time timestamp. I then had to call xenalyze with the core
> frequency
> defined so the timestamps made sence.
>
> Paul: Was there anything else you did I missed?
>
Sorry, I can't really comment, as I know few about this part of the
tracing infra, and nothing about ARM.
I do encourage Paul to chime in, but, actually, that would probably be
even easier when we'll have the code posted.
So, you know as they say in Open Source, don't you: release early,
release often! :-)
> > 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.
> For xenalyze I had to modify the makefile to build xenalyze on the
> ARM platform
> (it was specifically removed from the ARM build). Once that was
> corrected I
> could find and call it from dom0.
>
Great again!
> It built only locally to Xen though (could
> only run from dom0), I could not use it from the native Linux
> development
> environment (I don't know if you're supposed to be able to? Or since
> I'm running
> ARM it built for ARM not x86 and thus could not be used natively).
>
Yeah, well, if both dev and test environments are x86, I've done it a
couple of times, but I don't think its critical that we support that.
If architectures don't match, I actually think it is _the_right_thing_
that it does not work (as you say yourself)! :-)
> I plan to push they changes in as a patch to the mainline if that
> seems
> reasonable to everyone.
>
Looking forward to it. :-)
Thanks and 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-08 18:15 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 [this message]
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=1457460902.3102.282.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).