he
function as is.
Thanks,
Ben Sanda
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
any opinions on this?
How would you like to me proceed with this issue with regard to the
patch set? It sounds like this is a more far reaching architecture
design question for ARM. I have made the other changes to this version
of the code requested, should I submit v4? Or wait for a further
resolut
Andrew,
> Word your commit message like so:
>
> Signed-off-by: $ME
> ---
> CC: $SOMEONE
> CC: $SOMEONE_ELSE
>
> and `git send-email` will DTRT.
Ah, excellent. Then git send-email will auto add. Thanks,
I'll make the change for v4.
Ben
___
Xen-devel m
Jan,
> A couple of formal things: This is v3, and I only now notice
> indeed I should have looked at some of the patches. Yet which of them
> isn't clear - I'm being Cc-ed on all of them, instead of just the ones
> that submission guidelines say I should be. And then all patch
> subjects start wi
the patch names updated.
So then it is permissible to have multiple file changes in one
patch/commit? E.g. a patch that removes from one file and adds to
another in the same commit. I initially thought each patch/ commit was
only supposed to modify one file and that's why I did it that way
Should get_cyclces not use boot_count? I included it as the normal
system time call uses it so I assumed this should be consistent.
Thanks,
Ben Sanda
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
Julien and George,
Thank you for the comments. I had one question I wanted to ask.
>A DOMID_XEN page could be read only too. For instance, the meta-data
>of the trace buffer is read-only (see t_info), we don't want a domain
>to be able to overwrite them.
>However, all the foreign page are mapped
Konrad,
> Modified to provide support for xentrace on the ARM platform. Added
> flask credential to allow dom0 dom_xen mapping and write access for
> trace buffers.
>>
>> So .. what does that mean?
>>
>> Is that something xentrace requests? Why is this ARM specific?
>> Looking at xsm_sysctl and ho
Julien,
> Can you please CC the relevant maintainers in the next version of this series?
> You can use scripts/get_maintainers.pl for this purpose.
I did. The list output to me was:
Ian Jackson
Jan Beulich
Keir Fraser
Tim Deegan
I also added a few more that I had already
been in contact with
to correct this moving forward.
Thanks,
Ben
-Original Message-
From: Julien Grall [mailto:julien.gr...@arm.com]
Sent: 17 March, 2016 13:01
To: Ben Sanda ; xen-de...@lists.xenproject.org
Subject: Re: [Xen-devel] [PATCH 0/6] xentrace/xenalyze support on ARM
Hello Benjamin,
On 17/03/16 16:5
George,
Thank you for all the information. I'll take a dive in and see what I can see.
I'd at least like to get the CPU core frequency detection in as that will
make things a lot easier for us as we port to multiple platforms with
different cores. Then we don't have to keep looking up core speeds.
Paul,
>see the patch attached. It's a bit dirty still (that's why it wasn't
>upstreamed
>long time ago), but you can obviously look through it and gain some
>information.
Thanks, I’ll take a look and compare it against
mine to make sure we capture everything.
Ben
George,
>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
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).
I plan to push they changes in as a patch to the mainline if that seems
re
Paul,
Thank you very much for the reply. I’ll check out the fork for xenalyze.
I believe I have xentrace working now, mostly, but if possible I’d like to
see what you did on your build to get it working to compare. I
would like to push a patch into the mainline that agrees with both
of our effor
xenalyze.c, but no executable. 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?
Thank you,
Ben Sanda
___
Xen-devel mailing list
Xen-deve
]
Sent: 05 March, 2016 10:43
To: Ben Sanda ; xen-devel@lists.xen.org
Cc: Paul Sujkov
Subject: Re: [Xen-devel] Xentrace on Xilinx ARM
On Fri, 2016-03-04 at 20:53 +, Ben Sanda wrote:
> Hello,
>
Hello,
first of all, please, use plain text instead of HTML for emails to this list.
&
Hello,
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 sch
18 matches
Mail list logo
