On 12.12.18 19:59, Dario Faggioli wrote:
Yeah, and although difficult to admit/see the reason why, I think this
looks like it is coming from something we do in Xen. And since you say
you have an old Xen version that works, I really see bisection as the
way to go...
Not sure I'm getting. Are y
On Wed, 12 Dec 2018, Andrii Anisov wrote:
> Hello Stefano,
>
> On 12.12.18 19:39, Stefano Stabellini wrote:
> > Thanks for the good work, Andrii!
> >
> > The WARM_MAX improvements for vwfi=native with your optimizations are
> > impressive.
>
> I really hope you are not speaking about these numbe
On Wed, 2018-12-12 at 19:32 +0200, Andrii Anisov wrote:
> On 12.12.18 19:10, Dario Faggioli wrote:
> > I think only bisection could shed some light on this. And it would
> > be
> > wonderful if you could do that, but I understand that it takes
> > time. :-
> > /
> Well, bisect might help. But I'm r
Hello Stefano,
On 12.12.18 19:39, Stefano Stabellini wrote:
Thanks for the good work, Andrii!
The WARM_MAX improvements for vwfi=native with your optimizations are
impressive.
I really hope you are not speaking about these numbers:
max=840 warm_max=120 min=120 avg=127
Those are TBM barem
On Wed, 12 Dec 2018, Andrii Anisov wrote:
> On 12.12.18 11:46, Andrii Anisov wrote:
> > Digging into that now.
> I got it. My u-boot starts TBM in hyp mode. But them both miss setting
> HCR_EL2.IMO, so no interrupt exception was taken in hyp.
> OK, for my baremetal TBM in hyp, numbers are:
>
> max
Hello Dario,
On 12.12.18 19:10, Dario Faggioli wrote:
Ah, yes... I've seen the thread. I haven't commented, as it is really,
really weird, and I don't know what to think/say.
I think only bisection could shed some light on this. And it would be
wonderful if you could do that, but I understand t
On Wed, 2018-12-12 at 11:39 +0200, Andrii Anisov wrote:
> Hello Dario,
>
Hi,
> On 11.12.18 18:56, Dario Faggioli wrote:
> > Also, what about Xen numbers, sched=null.
> Didn't check, will put on the list.
>
:-)
> > I don't expect much improvement, considering pinning is in-place
> > already.
> A
On 12.12.18 11:46, Andrii Anisov wrote:
Digging into that now.
I got it. My u-boot starts TBM in hyp mode. But them both miss setting
HCR_EL2.IMO, so no interrupt exception was taken in hyp.
OK, for my baremetal TBM in hyp, numbers are:
max=840 warm_max=120 min=120 avg=127
I guess, warm_max
On 11.12.18 21:29, Stefano Stabellini wrote:
Yes, I think the uart driver could be sufficient, but it has only the
Xilinx uart, the pl011 and the Xen emergency console. If I recall
correctly, Renesas needs a different driver. Any platform specific
initialization would also need to be added to it
Hello Dario,
On 11.12.18 18:56, Dario Faggioli wrote:
Also, what about Xen numbers, sched=null.
Didn't check, will put on the list.
I don't expect much improvement, considering pinning is in-place
already.
Actually, I faced a strange issue with explicit pinning of Dom0. Didn't sort
out the
Hello Julien,
On 11.12.18 14:27, Julien Grall wrote:
I would like to have performance per patch so we can make the decisions whether
the implementation cost is worth it for upstream.
I'll check baremetal numbers first. Then will get numbers per patch.
--
Sincerely,
Andrii Anisov.
___
On Tue, 11 Dec 2018, Julien Grall wrote:
> On 11/12/2018 18:39, Stefano Stabellini wrote:
> > On Tue, 11 Dec 2018, Julien Grall wrote:
> > > On 10/12/2018 12:23, Andrii Anisov wrote:
> > > > Hello Julien,
> > > >
> > > > On 10.12.18 13:54, Julien Grall wrote:
> > > > > What are the numbers without
On 11/12/2018 18:39, Stefano Stabellini wrote:
On Tue, 11 Dec 2018, Julien Grall wrote:
On 10/12/2018 12:23, Andrii Anisov wrote:
Hello Julien,
On 10.12.18 13:54, Julien Grall wrote:
What are the numbers without Xen?
Good question. Didn't try. At least putchar should be implemented for tha
On Tue, 11 Dec 2018, Julien Grall wrote:
> On 10/12/2018 12:23, Andrii Anisov wrote:
> > Hello Julien,
> >
> > On 10.12.18 13:54, Julien Grall wrote:
> > > What are the numbers without Xen?
> > Good question. Didn't try. At least putchar should be implemented for that.
>
> I think we need the bar
On Tue, 2018-12-11 at 12:27 +, Julien Grall wrote:
> On 10/12/2018 12:23, Andrii Anisov wrote:
> > On 10.12.18 13:54, Julien Grall wrote:
> > > What are the numbers without Xen?
> > Good question. Didn't try. At least putchar should be implemented
> > for that.
>
> I think we need the baremeta
On 10/12/2018 12:23, Andrii Anisov wrote:
Hello Julien,
On 10.12.18 13:54, Julien Grall wrote:
What are the numbers without Xen?
Good question. Didn't try. At least putchar should be implemented for that.
I think we need the baremetal numbers to be able to compare properly the old and
new
Hello Julien,
On 10.12.18 13:54, Julien Grall wrote:
What are the numbers without Xen?
Good question. Didn't try. At least putchar should be implemented for that.
Which version of Xen are you using?
This morning's staging, commit-id 58eb90a9650a8ea73533bc2b87c13b8ca7bbe35a.
This also tells
(sorry for the formatting)
On Mon, 10 Dec 2018, 12:00 Andrii Anisov, wrote:
> Hello All,
>
> On 27.11.18 23:27, Stefano Stabellini wrote:
> > See the following:
> >
> > https://marc.info/?l=xen-devel&m=148668817704668
> So I did port that stuff to the current staging [1].
> Also, the corresponde
Hello All,
On 27.11.18 23:27, Stefano Stabellini wrote:
See the following:
https://marc.info/?l=xen-devel&m=148668817704668
So I did port that stuff to the current staging [1].
Also, the correspondent tbm, itself is here [2].
Having 4 big cores on my SoC I run XEN with the following command li
Hello Stefano,
On 27.11.18 23:27, Stefano Stabellini wrote:
Hi Andrii,
See the following:
https://marc.info/?l=xen-devel&m=148668817704668
Thank you for the point. I remember this email, but missed it also gives
details to setup the experiment. It looks that bare-metal app is not SoC
specifi
On Tue, 20 Nov 2018, Andrii Anisov wrote:
> Hello Stefano,
>
> On 01.11.18 22:20, Stefano Stabellini wrote:
> > No, I haven't had any time. Aside from the Xen version, another
> > difference is the interrupt source. I used the physical timer for
> > testing.
>
> Could you share your approach for
Hello Stefano,
On 01.11.18 22:20, Stefano Stabellini wrote:
No, I haven't had any time. Aside from the Xen version, another
difference is the interrupt source. I used the physical timer for
testing.
Could you share your approach for interrupts latency measurement? Are
you using any HW specifi
Hi Dario,
On 09/10/2018 17:46, Dario Faggioli wrote:
On Tue, 2018-10-09 at 12:59 +0200, Milan Boberic wrote:
Hi,
Hi Milan,
I'm testing Xen Hypervisor 4.10 performance on UltraZed-EG board with
carrier card.
I created bare-metal application in Xilinx SDK.
In bm application I:
- s
Hi Stefano,
On 11/1/18 8:20 PM, Stefano Stabellini wrote:
On Wed, 31 Oct 2018, Julien Grall wrote:
On 10/31/18 8:35 PM, Milan Boberic wrote:
Hi,
Interesting. Could you confirm the commit you were using (or the point
release)?
Stefano's number were based on commit "fuzz: update README.afl exa
On Wed, 31 Oct 2018, Julien Grall wrote:
> On 10/31/18 8:35 PM, Milan Boberic wrote:
> > Hi,
> >
> > > Interesting. Could you confirm the commit you were using (or the point
> > > release)?
> > > Stefano's number were based on commit "fuzz: update README.afl example"
> > > 55a04feaa1f8ab6ef7d723fb
On 10/31/18 8:35 PM, Milan Boberic wrote:
Hi,
Interesting. Could you confirm the commit you were using (or the point
release)?
Stefano's number were based on commit "fuzz: update README.afl example"
55a04feaa1f8ab6ef7d723fbb1d39c6b96ad184a which is an unreleased version
of Xen.
All Xens I u
Hi,
> Interesting. Could you confirm the commit you were using (or the point
> release)?
> Stefano's number were based on commit "fuzz: update README.afl example"
> 55a04feaa1f8ab6ef7d723fbb1d39c6b96ad184a which is an unreleased version
> of Xen.
All Xens I used are from Xilinx git repository bec
Hi Milan,
On 10/29/18 12:29 PM, Milan Boberic wrote:
Sorry for late reply,
Don't worry, thank you for the testing and sending the .config.
I am afraid no. .config is generated during building time. So can you
paste here please.
".config" file is in attachment.
I also tried Xen 4.9 and
Sorry for late reply,
> I am afraid no. .config is generated during building time. So can you
> paste here please.
".config" file is in attachment.
I also tried Xen 4.9 and I got almost same numbers, jitter is smaller
by 150ns which isn't significant change at all.
Milan
#
# Automatically gene
On Fri, 26 Oct 2018, Julien Grall wrote:
> Hi Stefano,
>
> On 10/25/18 5:15 PM, Stefano Stabellini wrote:
> > On Thu, 25 Oct 2018, Julien Grall wrote:
> > > Hi Stefano,
> > >
> > > On 10/24/18 1:24 AM, Stefano Stabellini wrote:
> > > > On Tue, 23 Oct 2018, Milan Boberic wrote:
> > > > I don't hav
Hi Stefano,
On 10/25/18 5:15 PM, Stefano Stabellini wrote:
On Thu, 25 Oct 2018, Julien Grall wrote:
Hi Stefano,
On 10/24/18 1:24 AM, Stefano Stabellini wrote:
On Tue, 23 Oct 2018, Milan Boberic wrote:
I don't have any other things to suggest right now. You should be able
to measure an overall
On Thu, 25 Oct 2018, Julien Grall wrote:
> Hi Stefano,
>
> On 10/24/18 1:24 AM, Stefano Stabellini wrote:
> > On Tue, 23 Oct 2018, Milan Boberic wrote:
> > I don't have any other things to suggest right now. You should be able
> > to measure an overall 2.5us IRQ latency (if the interrupt rate is n
On 10/25/18 3:47 PM, Milan Boberic wrote:
I was asking the Xen configuration (xen/.config) to know what you have
enabled in Xen.
Oh, sorry, because I'm building xen from git repository here is the
link to it where you can check the file you mentioned.
https://github.com/Xilinx/xen/tree/xilin
> I was asking the Xen configuration (xen/.config) to know what you have
> enabled in Xen.
Oh, sorry, because I'm building xen from git repository here is the
link to it where you can check the file you mentioned.
https://github.com/Xilinx/xen/tree/xilinx/versal/xen
> It might, OTOH, be wise to
On 10/25/18 1:36 PM, Milan Boberic wrote:
On Thu, Oct 25, 2018 at 1:30 PM Julien Grall wrote:
Hi Milan,
Hi Julien,
Sorry if it was already asked. Can you provide your .config for your
test?
Yes of course, bare-metal's .cfg file is in it's in attachment (if
that is what you asked :) ).
Hi Dario,
On 10/25/18 2:44 PM, Dario Faggioli wrote:
On Thu, 2018-10-25 at 14:36 +0200, Milan Boberic wrote:
On Thu, Oct 25, 2018 at 1:30 PM Julien Grall
wrote:
Do you have DEBUG enabled?
I'm not sure where exactly should I disable it. If you check line 18
in xl dmesg file in attachment i
On Thu, 2018-10-25 at 14:36 +0200, Milan Boberic wrote:
> On Thu, Oct 25, 2018 at 1:30 PM Julien Grall
> wrote:
> > Do you have DEBUG enabled?
>
> I'm not sure where exactly should I disable it. If you check line 18
> in xl dmesg file in attachment it says debug=n, it's output of xl
> dmesg. I'm
On Thu, Oct 25, 2018 at 1:30 PM Julien Grall wrote:
>
> Hi Milan,
Hi Julien,
> Sorry if it was already asked. Can you provide your .config for your
> test?
Yes of course, bare-metal's .cfg file is in it's in attachment (if
that is what you asked :) ).
> Do you have DEBUG enabled?
I'm not sur
Hi Milan,
On 10/25/18 11:09 AM, Milan Boberic wrote:
Hi,
On Wed, Oct 24, 2018 at 2:24 AM Stefano Stabellini
wrote:
It is good that there are no physical interrupts interrupting the cpu.
serrors=panic makes the context switch faster. I guess there are not
enough context switches to make a meas
Hi Stefano,
On 10/24/18 1:24 AM, Stefano Stabellini wrote:
On Tue, 23 Oct 2018, Milan Boberic wrote:
I don't have any other things to suggest right now. You should be able
to measure an overall 2.5us IRQ latency (if the interrupt rate is not
too high).
Is it number you measured on Xen 4.11 fla
Hi,
> On Wed, Oct 24, 2018 at 2:24 AM Stefano Stabellini
> wrote:
> It is good that there are no physical interrupts interrupting the cpu.
> serrors=panic makes the context switch faster. I guess there are not
> enough context switches to make a measurable difference.
Yes, when I did:
grep ctxt
On Tue, 23 Oct 2018, Milan Boberic wrote:
> > Just add an && irq != 1023 to the if check.
> Added it and now when I create bare-metal guest it prints only once:
>
> (XEN) DEBUG irq=0
> (XEN) d1v0 No valid vCPU found for vIRQ32 in the target list (0x2). Skip it
> (XEN) d1v0 No valid vCPU found for
> Just add an && irq != 1023 to the if check.
Added it and now when I create bare-metal guest it prints only once:
(XEN) DEBUG irq=0
(XEN) d1v0 No valid vCPU found for vIRQ32 in the target list (0x2). Skip it
(XEN) d1v0 No valid vCPU found for vIRQ33 in the target list (0x2). Skip it
(XEN) d1v0 No
On Mon, 22 Oct 2018, Milan Boberic wrote:
> Hi,
>
> > I think we want to fully understand how many other interrupts the
> > baremetal guest is receiving. To do that, we can modify my previous
> > patch to suppress any debug messages for virq=68. That way, we should
> > only see the other interrupt
Hi,
> I think we want to fully understand how many other interrupts the
> baremetal guest is receiving. To do that, we can modify my previous
> patch to suppress any debug messages for virq=68. That way, we should
> only see the other interrupts. Ideally there would be none.
> diff --git a/xen/arc
On Fri, 2018-10-19 at 14:02 -0700, Stefano Stabellini wrote:
> On Wed, 17 Oct 2018, Milan Boberic wrote:
> > I checked interrupt frequency with oscilloscope
> > just to be sure (toggling LED on/off when interrupts occur). So,
> > when I set:
> > - interrupts to be generated every 8 us I get jitter
On Wed, 17 Oct 2018, Milan Boberic wrote:
> Hi,
> >
> > The device tree with everything seems to be system.dts, that was enough
> > :-) I don't need the dtsi files you used to build the final dts, I only
> > need the one you use in uboot and for your guest.
>
> I wasn't sure so I sent everything
Hi,
>
> The device tree with everything seems to be system.dts, that was enough
> :-) I don't need the dtsi files you used to build the final dts, I only
> need the one you use in uboot and for your guest.
I wasn't sure so I sent everything, sorry for being bombarded with
all those files. :-)
>
On 10/13/2018 05:01 PM, Milan Boberic wrote:
Hi,
Hi,
Don't interrupt _come_ from hardware and go/are routed to
hypervisor/os/app?
Yes they do, sorry, I reversed the order because I'm a newbie :) .
Would you mind to explain what is the triple timer counter?
On this link on page 342 is
On Mon, 15 Oct 2018, Milan Boberic wrote:
> In attachment are device-tree files I found in my project:
>
> device-tree.bbappend - under
> /uz3eg_iocc_2018_2/project-spec/meta-user/recipes-bsp/device-tree/
>
> xen-overlay.dtsi , system-user.dtsi and zunqmp-qemu-arm.dts - under
> /uz3eg_iocc_2018_2
On 15/10/2018 14:01, Milan Boberic wrote:
On 15/10/2018 09:14, Julien Grall wrote:
Which link?
I made hyperlink on "link" word, looks like somehow it got lost, here
is the link:
https://www.xilinx.com/support/documentation/user_guides/ug1085-zynq-ultrascale-trm.pdf
HTML should be avoided o
> On 15/10/2018 09:14, Julien Grall wrote:
> Which link?
I made hyperlink on "link" word, looks like somehow it got lost, here
is the link:
https://www.xilinx.com/support/documentation/user_guides/ug1085-zynq-ultrascale-trm.pdf
> The board should be fully supported upstreamed. If Xilinx has more
(Resending with a different address)
On 15/10/2018 09:14, Julien Grall wrote:
On 10/13/2018 05:01 PM, Milan Boberic wrote:
Hi,
Hi,
Don't interrupt _come_ from hardware and go/are routed to
hypervisor/os/app?
Yes they do, sorry, I reversed the order because I'm a newbie :) .
Would you
On Sat, 13 Oct 2018, Milan Boberic wrote:
> > This is definitely wrong. Can you please also post the full host device
> > tree with your modifications that you are using for Xen and Dom0? You
> > should have something like:
> >
> > timer@ff11 {
> > compatible = "cdns,ttc";
Hi,
> Don't interrupt _come_ from hardware and go/are routed to
> hypervisor/os/app?
Yes they do, sorry, I reversed the order because I'm a newbie :) .
> Would you mind to explain what is the triple timer counter?
On this link on page 342 is explanation.
> This is not the official Xen repository
On Fri, 12 Oct 2018, Milan Boberic wrote:
> Hi Stefano, glad to have you back :D,
> this is my setup:
> - dom0 is PetaLinux, has 1 vCPU and it's pinned for pCPU0
> - there is only one domU and this is my bare-metal app that also have
> one vCPU and it's pinned for pCPU1
> so yeah,
Hi,
Sorry for the formatting.
On Fri, 12 Oct 2018, 17:36 Milan Boberic, wrote:
> Hi Stefano, glad to have you back :D,
> this is my setup:
> - dom0 is PetaLinux, has 1 vCPU and it's pinned for pCPU0
> - there is only one domU and this is my bare-metal app that also
> have one vC
Hi Stefano, glad to have you back :D,
this is my setup:
- dom0 is PetaLinux, has 1 vCPU and it's pinned for pCPU0
- there is only one domU and this is my bare-metal app that also
have one vCPU and it's pinned for pCPU1
so yeah, there is only dom0 and bare-metal app on the board.
Ji
On Thu, 11 Oct 2018, Milan Boberic wrote:
> On Wed, Oct 10, 2018 at 6:41 PM Meng Xu wrote:
> >
> > The jitter may come from Xen or the OS in dom0.
> > It will be useful to know what is the jitter if you run the test on
> > PetaLinux.
> > (It's understandable the jitter is gone without OS. It is a
Hey,
Be a bit more careful about not top posting, please? :-)
On Thu, 2018-10-11 at 14:17 +0200, Milan Boberic wrote:
> I misunderstood the passthrough concept, it only allows guest domain
> to use certain interrupts and memory.
>
I'm afraid we totally rely on people with much more experience th
Hi Milan,
On Thu, Oct 11, 2018 at 12:36 AM Milan Boberic wrote:
>
> On Wed, Oct 10, 2018 at 6:41 PM Meng Xu wrote:
> >
> > The jitter may come from Xen or the OS in dom0.
> > It will be useful to know what is the jitter if you run the test on
> > PetaLinux.
> > (It's understandable the jitter i
I misunderstood the passthrough concept, it only allows guest domain
to use certain interrupts and memory. Is there are way to somehow
route interrupt from domU (bare-metal app) to hw?
On Thu, Oct 11, 2018 at 9:36 AM Milan Boberic wrote:
>
> On Wed, Oct 10, 2018 at 6:41 PM Meng Xu wrote:
> >
> >
On Wed, Oct 10, 2018 at 6:41 PM Meng Xu wrote:
>
> The jitter may come from Xen or the OS in dom0.
> It will be useful to know what is the jitter if you run the test on PetaLinux.
> (It's understandable the jitter is gone without OS. It is also common
> that OS introduces various interferences.)
[Just add some thoughts on this.]
On Wed, Oct 10, 2018 at 4:22 AM Milan Boberic wrote:
>
> Hi,
> sorry, my explanation wasn't precise and I missed the point.
> vCPU pinning with sched=null I put "just in case", because it doesn't hurt.
>
> Yes, PetaLinux domain is dom0.
The jitter may come from
Attachments.
name = "test"
kernel = "timer.bin"
memory = 8
vcpus = 1
cpus = [1]
irqs = [ 48, 54, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79 ]
iomem = [ "0xff010,1", "0xff110,1", "0xff120,1", "0xff130,1", "0xff140,1",
"0xff0a0,1" ][0.00] Booting Linux on physical CPU 0x0
[0.00]
Hi,
sorry, my explanation wasn't precise and I missed the point.
vCPU pinning with sched=null I put "just in case", because it doesn't hurt.
Yes, PetaLinux domain is dom0.
Tested with Credit scheduler before (it was just the LED blink
application but anyway), it results with bigger jitter then nu
On Tue, 2018-10-09 at 12:59 +0200, Milan Boberic wrote:
> Hi,
>
Hi Milan,
> I'm testing Xen Hypervisor 4.10 performance on UltraZed-EG board with
> carrier card.
> I created bare-metal application in Xilinx SDK.
> In bm application I:
>- start triple timer counter (ttc) which generates
67 matches
Mail list logo
