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

[Stefano Stabellini <sstabellini@xxxxxxxxxx>]

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    3420    2650
> > > > > NODEBUG WFI credit2     8080    7890    10320   8300
> > > > > 
> > > > > DEBUG no WFI            2252    2080    3320    2650
> > > > > DEBUG WFI               6500    6140    8520    8130
> > > > > DEBUG WFI, credit2      8050    7870    10680   8450
> > > > > 
> > > > > DEBUG means Xen DEBUG build.
> > > > > 
> > [...]
> > > > > As you can see, depending on whether the guest issues a WFI or
> > > > > not
> > > > > while
> > > > > waiting for interrupts, the results change significantly.
> > > > > Interestingly,
> > > > > credit2 does worse than credit1 in this area.
> > > > > 
> > > > This is with current staging right? 
> > > 
> > > That's right.
> > > 
> > So, when you have the chance, can I see the output of
> > 
> >  xl debug-key r
> >  xl dmesg
> > 
> > Both under Credit1 and Credit2?
> 
> I'll see what I can do.

See attached.

Attachment: konsole.credit1.log.2
Description: Text document

Attachment: konsole.credit2.log.2
Description: Text document

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