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

["Xu, YongweiX" <yongweix.xu@xxxxxxxxx>]

> -----Original Message-----
> From: Jan Beulich [mailto:JBeulich@xxxxxxxx]
> Sent: Tuesday, September 17, 2013 2:39 PM
> To: Xu, YongweiX
> Cc: Joby Poriyath; Sander Eikelenboom; Zhou, Chao; Liu, SongtaoX; xen-devel
> Subject: RE: [Xen-devel] [PATCH v8] interrupts: allow guest to set/clear MSI-X
> mask bit
> 
> >>> On 17.09.13 at 05:06, "Xu, YongweiX" <yongweix.xu@xxxxxxxxx> wrote:
> > I've provided 'i' an 'M' debug key to output the IRQ and MSI-X
> > information, the 'xl dmesg'log of dom0 as the attachment:xl_dmesg.log.
> 
> Nothing odd there, but then again you also still didn't tell us which IRQ it 
> is that
> gets switched off by the guest kernel. Even without me saying so explicitly, 
> it
> should be pretty clear that sending complete information (matching up
> hypervisor, host, and guest
> logs) ideally limited to just one guest instance (the log here has 6
> guests) would provide the maximum information. Remember that unless you're
> going to debug the problem yourself, we depend on the information coming
> from you being complete and consistent.
> In the case at hand, telling us whether the log was taken with a VF or PF
> assigned would also be relevant information (which would presumably be
> deducible from the guest kernel log if you had sent it).

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！

 
> > Retested by changing the guest kernel to 3.11.1, the issue not exist.
> > But
> > rhel6.4 is a mainstream distribution, so I think we must take care of it.
> 
> Sure, but the direction of where to look for the problem may be different. It
> might e.g. be the case that the old driver handles the VF reset differently,
> which might direct us to revisit the unmasking done by the patch.
> 
> In any event - any debugging _you_ can do would likely get us to make faster
> progress on this...

Attachment: dom_xl_dmesg.log
Description: dom_xl_dmesg.log

Attachment: guest_dmesg.log
Description: guest_dmesg.log

Attachment: guest_messages.log
Description: guest_messages.log

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