From: George Dunlap <george.dunlap@citrix.com>
To: Ben Sanda <Ben.Sanda@dornerworks.com>,
Dario Faggioli <dario.faggioli@citrix.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 18:44:51 +0000 [thread overview]
Message-ID: <56DF1DA3.5000007@citrix.com> (raw)
In-Reply-To: <A2A949C387F3A54C9B4DAC2DCD2E9A85C38D53E7@Quimby.dw.local>
On 08/03/16 18:04, 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.
>
> 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.
FWIW, on my "to-do" list for xenalyze for years has been to have the
xentrace process query something (either Xen or Linux) to find the hz
rate, and then write that at the beginning of the xentrace file, so that
xenalyze could just pick that up and use it. Since you're doing some
work on xentrace / xenalyze anyway, you might think about adding that to
your "to-do" list -- it doesn't seem conceptually like it would be that
hard.
The other thing that might be useful is information about the
architecture you're running on -- right now it assumes intel, and will
crash tracing a file generated on an AMD box unless you specify
--svm-mode. Adding a trace record that indicates "Intel / AMD / ARM"
would also make things a lot easier.
> I plan to push they changes in as a patch to the mainline if that seems
> reasonable to everyone.
Yes, please. :-)
-George
_______________________________________________
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:44 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
2016-03-08 18:44 ` George Dunlap [this message]
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=56DF1DA3.5000007@citrix.com \
--to=george.dunlap@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).