Re: [Xen-devel] [PATCH v8] interrupts: allow guest to set/clear MSI-X mask bit

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 18.09.13 at 05:19, "Xu, YongweiX" <yongweix.xu@xxxxxxxxx> wrote:
> I've retested this issue for many times, but can only get these log as 
> attachment, it can only be found IRQ #50 issue on guest but cannot found on 
> Dom0 "xl dmesg" log, if you think it's still lack of persuasion, do you have 
> any method or patch to capture more IRQ information? thanksï

The paired up logs at least allows us to guess that it's only the
third of the three interrupts the driver sets up that causes the
problem.

Looking at the plain 2.6.32 driver sources likely will make little
sense, as the RHEL kernel is presumably heavily patched, and
as I don't know that driver anyway. So getting someone of
your LAD folks involved might be a good idea, even if just to
explain what the driver and hardware behavior here are, and
what the individual IRQs are actually used for (judging from
3.12-rc1, the IRQ use is for RX, TX, and "other", whatever
"other" means, and looking at the 2.6.32 and 3.12-rc1
variants of e1000_msix_other() they look rather similar, so
the problem must be associated with something elsewhere in
the driver).

Interestingly enough the other two IRQ handlers don't have a
check resulting in them returning IRQ_NONE. Could you double
check what the counts of all three interrupts are in the guest's
/proc/interrupts?

Jan

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