Re: [Xen-devel] Xen on ARM IRQ latency and scheduler overhead

2017-02-20 Thread Punit Agrawal
Dario Faggioli writes: > On Fri, 2017-02-17 at 19:44 +, Julien Grall wrote: >> On 02/17/2017 06:40 PM, Dario Faggioli wrote: >> > Does ARM >> > have frequency scaling (I did remember something on xen-devel, but >> > I am >> > not sure whether it landed upstream)? >> >> I guess you mean the s

Re: [Xen-devel] Xen on ARM IRQ latency and scheduler overhead

2017-02-20 Thread Dario Faggioli
On Mon, 2017-02-20 at 11:04 +, George Dunlap wrote: > On 18/02/17 00:41, Stefano Stabellini wrote: > > > > On Fri, 17 Feb 2017, Dario Faggioli wrote: > > > cyclictest 1us cyclictest 1ms cyclictest > > > 100ms > > > (cycles) Credit1 Credit2 Credit1 Cred > > >

Re: [Xen-devel] Xen on ARM IRQ latency and scheduler overhead

2017-02-20 Thread George Dunlap
On 18/02/17 00:41, Stefano Stabellini wrote: > On Fri, 17 Feb 2017, Dario Faggioli wrote: >> On Thu, 2017-02-09 at 16:54 -0800, Stefano Stabellini wrote: >>> These are the results, in nanosec: >>> >>> AVG MIN MAX WARM MAX >>> >>> NODEBUG no WFI 18901

Re: [Xen-devel] Xen on ARM IRQ latency and scheduler overhead

2017-02-17 Thread Dario Faggioli
On Fri, 2017-02-17 at 19:44 +, Julien Grall wrote: > On 02/17/2017 06:40 PM, Dario Faggioli wrote: > > Does ARM > > have frequency scaling (I did remember something on xen-devel, but > > I am > > not sure whether it landed upstream)? > > I guess you mean the series sent by globallogic ([1])? I

Re: [Xen-devel] Xen on ARM IRQ latency and scheduler overhead

2017-02-17 Thread Dario Faggioli
On Fri, 2017-02-17 at 16:02 -0800, Stefano Stabellini wrote: > On Fri, 17 Feb 2017, Stefano Stabellini wrote: > >  > > NODEBUG vwfi=idle credit2 fix cpumasks 40002370 > > 45003350 > > NODEBUG vwfi=idle credit1 fix cpumasks 32202180 > > 45004320 > > Actuall

Re: [Xen-devel] Xen on ARM IRQ latency and scheduler overhead

2017-02-17 Thread Stefano Stabellini
On Fri, 17 Feb 2017, Dario Faggioli wrote: > On Thu, 2017-02-09 at 16:54 -0800, Stefano Stabellini wrote: > > These are the results, in nanosec: > > > >     AVG MIN MAX WARM MAX > > > > NODEBUG no WFI  1890    1800    3170    2070 > > NODEBUG WFI   

Re: [Xen-devel] Xen on ARM IRQ latency and scheduler overhead

2017-02-17 Thread Stefano Stabellini
On Fri, 17 Feb 2017, Stefano Stabellini wrote: > On Fri, 17 Feb 2017, Julien Grall wrote: > > Hi, > > > > On 02/17/2017 11:02 AM, Dario Faggioli wrote: > > > Just very quickly... > > > > > > On Thu, 2017-02-16 at 15:07 -0800, Stefano Stabellini wrote: > > > > (XEN) Active queues: 1 > > > > (XEN)

Re: [Xen-devel] Xen on ARM IRQ latency and scheduler overhead

2017-02-17 Thread Stefano Stabellini
On Fri, 17 Feb 2017, Julien Grall wrote: > Hi, > > On 02/17/2017 11:02 AM, Dario Faggioli wrote: > > Just very quickly... > > > > On Thu, 2017-02-16 at 15:07 -0800, Stefano Stabellini wrote: > > > (XEN) Active queues: 1 > > > (XEN) default-weight = 256 > > > (XEN) Runqueue 0: > > > (XEN)

Re: [Xen-devel] Xen on ARM IRQ latency and scheduler overhead

2017-02-17 Thread Stefano Stabellini
On Fri, 17 Feb 2017, Julien Grall wrote: > Hi Dario, > > On 02/17/2017 06:40 PM, Dario Faggioli wrote: > > On Thu, 2017-02-09 at 16:54 -0800, Stefano Stabellini wrote: > > Actually, TSC on this box should be stable and invariant, so I guess I > > can try with the default governor. Will do that on

Re: [Xen-devel] Xen on ARM IRQ latency and scheduler overhead

2017-02-17 Thread Julien Grall
Hi Dario, On 02/17/2017 06:40 PM, Dario Faggioli wrote: On Thu, 2017-02-09 at 16:54 -0800, Stefano Stabellini wrote: Actually, TSC on this box should be stable and invariant, so I guess I can try with the default governor. Will do that on Monday. Does ARM have frequency scaling (I did remember s

Re: [Xen-devel] Xen on ARM IRQ latency and scheduler overhead

2017-02-17 Thread Julien Grall
Hi, On 02/17/2017 11:02 AM, Dario Faggioli wrote: Just very quickly... On Thu, 2017-02-16 at 15:07 -0800, Stefano Stabellini wrote: (XEN) Active queues: 1 (XEN) default-weight = 256 (XEN) Runqueue 0: (XEN) ncpus = 4 (XEN) cpus = 0-3 (XEN) max_weight

Re: [Xen-devel] Xen on ARM IRQ latency and scheduler overhead

2017-02-17 Thread Dario Faggioli
On Thu, 2017-02-09 at 16:54 -0800, Stefano Stabellini wrote: > These are the results, in nanosec: > >     AVG MIN MAX WARM MAX > > NODEBUG no WFI  1890    1800    3170    2070 > NODEBUG WFI 4850    4810    7030    4980 > NODEBUG no WFI credit2 

Re: [Xen-devel] Xen on ARM IRQ latency and scheduler overhead

2017-02-17 Thread Dario Faggioli
Just very quickly... On Thu, 2017-02-16 at 15:07 -0800, Stefano Stabellini wrote: > (XEN) Active queues: 1 > (XEN)   default-weight = 256 > (XEN) Runqueue 0: > (XEN)   ncpus  = 4 > (XEN)   cpus   = 0-3 > (XEN)   max_weight = 256 > (XEN)   instload   = 1

Re: [Xen-devel] Xen on ARM IRQ latency and scheduler overhead

2017-02-16 Thread Stefano Stabellini
On Thu, 16 Feb 2017, Stefano Stabellini wrote: > > > > >     AVG MIN MAX WARM MAX > > > > > > > > > > NODEBUG no WFI  1890    1800    3170    2070 > > > > > NODEBUG WFI 4850    4810    7030    4980 > > > > > NODEBUG no WFI credit2  2217    2090  

Re: [Xen-devel] Xen on ARM IRQ latency and scheduler overhead

2017-02-16 Thread Stefano Stabellini
On Thu, 16 Feb 2017, Dario Faggioli wrote: > On Fri, 2017-02-10 at 10:32 -0800, Stefano Stabellini wrote: > > On Fri, 10 Feb 2017, Dario Faggioli wrote: > > > Right, interesting use case. I'm glad to see there's some interest > > > in > > > it, and am happy to help investigating, and trying to make

Re: [Xen-devel] Xen on ARM IRQ latency and scheduler overhead

2017-02-16 Thread Dario Faggioli
On Fri, 2017-02-10 at 10:32 -0800, Stefano Stabellini wrote: > On Fri, 10 Feb 2017, Dario Faggioli wrote: > > Right, interesting use case. I'm glad to see there's some interest > > in > > it, and am happy to help investigating, and trying to make things > > better. > > Thank you! > Hey, FYI, I am

Re: [Xen-devel] Xen on ARM IRQ latency and scheduler overhead

2017-02-10 Thread Stefano Stabellini
On Fri, 10 Feb 2017, Dario Faggioli wrote: > On Thu, 2017-02-09 at 16:54 -0800, Stefano Stabellini wrote: > > Hi all, > > > Hi, > > > I have run some IRQ latency measurements on Xen on ARM on a Xilinx > > ZynqMP board (four Cortex A53 cores, GICv2). > > > > Dom0 has 1 vcpu pinned to cpu0, DomU h

Re: [Xen-devel] Xen on ARM IRQ latency and scheduler overhead

2017-02-10 Thread Dario Faggioli
On Thu, 2017-02-09 at 16:54 -0800, Stefano Stabellini wrote: > Hi all, > Hi, > I have run some IRQ latency measurements on Xen on ARM on a Xilinx > ZynqMP board (four Cortex A53 cores, GICv2). > > Dom0 has 1 vcpu pinned to cpu0, DomU has 1 vcpu pinned to cpu2. > Dom0 is Ubuntu. DomU is an ad-hoc

[Xen-devel] Xen on ARM IRQ latency and scheduler overhead

2017-02-09 Thread Stefano Stabellini
Hi all, I have run some IRQ latency measurements on Xen on ARM on a Xilinx ZynqMP board (four Cortex A53 cores, GICv2). Dom0 has 1 vcpu pinned to cpu0, DomU has 1 vcpu pinned to cpu2. Dom0 is Ubuntu. DomU is an ad-hoc baremetal app to measure interrupt latency: https://github.com/edgarigl/tbm I