>>> On 18.06.15 at 11:18, <yang.z.zh...@intel.com> wrote: > Jan Beulich wrote on 2015-06-18: >>>>> On 18.06.15 at 10:53, <yang.z.zh...@intel.com> wrote: >>> Jan Beulich wrote on 2015-06-18: >>>>>>> On 18.06.15 at 10:20, <jbeul...@suse.com> wrote: >>>>> Apart from that I notice that the EXIT_REASON_EOI_INDUCED handling >>>>> also adds about the same number of ticks... >>>> >>>> Are there any other devices in the guest causing meaningful amounts >>>> of interrupts (I suppose the SSD itself is using just one)? I ask >>>> since I wonder whether e.g. there may be lock contention in >> vioapic_update_EOI(). >>> >>> The EXIT_REASON_EOI_INDUCED is for local apic time. >> >> ??? (I.e. I don't see the connection between the context and your reply. >> Perhaps I'm missing something obvious...) > > I mean the lots of EXIT_REASON_EOI_INDUCEDis for local apic time which is > edge-trigger. So it will not call vioapic_update_EOI.
Okay, this then suggests the problem being hvm_dpci_msi_eoi(), albeit looking at it I can't immediately see why it would take long. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
