xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ben Sanda <Ben.Sanda@dornerworks.com>
To: Dario Faggioli <dario.faggioli@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: Paul Sujkov <psujkov@gmail.com>
Subject: Re: Xentrace on Xilinx ARM
Date: Mon, 7 Mar 2016 03:20:10 +0000	[thread overview]
Message-ID: <A2A949C387F3A54C9B4DAC2DCD2E9A85C38D52C0@Quimby.dw.local> (raw)
In-Reply-To: <1457192589.2959.603.camel@citrix.com>

Dario,

Thank you very much for the help. I apologize for the HTML output on
the first email, I thought I had outlook set to send it in plain text.
My mistake. 

> Well, in this other thread, Paul (Cc-ed) says he basically has tracing working on ARM:

> http://lists.xenproject.org/archives/html/xen-devel/2016-02/msg03373.html

I hadn't found that thread by Paul thank you for pointing it out. I would be eager to
see what additional changes he had to make to get it actually working.
It sounds like we headed down the same path, but there's more needed
that I'm unaware of.

Paul, I would be eager to see what changes you had to make to get
xentrace working on ARM and compare that against what I've tried. If
we could push up a formal patch that would be excellent.

Thanks,
Ben

-----Original Message-----
From: Dario Faggioli [mailto:dario.faggioli@citrix.com] 
Sent: 05 March, 2016 10:43
To: Ben Sanda <Ben.Sanda@dornerworks.com>; xen-devel@lists.xen.org
Cc: Paul Sujkov <psujkov@gmail.com>
Subject: Re: [Xen-devel] Xentrace on Xilinx ARM

On Fri, 2016-03-04 at 20:53 +0000, Ben Sanda wrote:
> Hello,
>  
Hello,

first of all, please, use plain text instead of HTML for emails to this list.

> My name is Ben Sanda, I’m a kernel/firmware developer with DornerWorks 
> engineering. Our team is working on support for Xen on the new Xilinx
> Ultrascale+ MPSoC platforms (ARM A53 core) and I’ve specifically been
> tasked
> with characterizing performance, particularly that of the schedulers.
> I wanted
> to make use of the xentrace tool to help give us some timing and 
> performance benchmarks, but searching over the Xen mailing lists it 
> appears xentrace has not yet been ported to ARM.
>
No, tracing support for ARM is not present upstream
 
> In searching for existing topics on this my main reference thread for 
> this has been the “[Xen-devel] xentrace, arm, hvm” email chain started 
> by Pavlo Suikov
> here: http://xen.markmail.org/thread/zochggqxcifs5cdi
> 
Well, in this other thread, Paul (Cc-ed) says he basically has tracing working on ARM:

http://lists.xenproject.org/archives/html/xen-devel/2016-02/msg03373.html

Any chance you maybe to can cooperate to get such support upstream?
That would be reallyy cool. :-)

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)

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-03-07  3:20 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 [this message]
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
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=A2A949C387F3A54C9B4DAC2DCD2E9A85C38D52C0@Quimby.dw.local \
    --to=ben.sanda@dornerworks.com \
    --cc=dario.faggioli@citrix.com \
    --cc=psujkov@gmail.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).