Re: [Xen-devel] Xen-unstable: pci-passthrough of device using MSI-X interrupts not working after commit x86/MSI: track host and guest masking separately

[linux@xxxxxxxxxxxxxx]

On 2015-06-26 11:56, Jan Beulich wrote:
> > > > On 25.06.15 at 14:02, <linux@xxxxxxxxxxxxxx> wrote:
> > Thursday, June 25, 2015, 1:29:39 PM, you wrote:
> > > > > > On 25.06.15 at 12:51, <linux@xxxxxxxxxxxxxx> wrote:
> > > > Attached is the xl-dmesg output of:
> > > >
> > > > - debug-keys M and i before guest boot
> > > > - guest boot
> > > > - debug-keys M and i after lsusb in the guest that hangs.
> > > Interesting:
> > > (XEN) [2015-06-25 10:46:31.820]  MSI-X   84 vec=aa lowest  edge   
> > > assert  log
> > lowest dest=00000002 mask=1/ G/1
> > > (XEN) [2015-06-25 10:46:31.820]  MSI-X   85 vec=b2 lowest  edge   
> > > assert  log
> > lowest dest=00000002 mask=1/ G/1
> > > (XEN) [2015-06-25 10:46:31.820]  MSI-X   86 vec=ba lowest  edge   
> > > assert  log
> > lowest dest=00000002 mask=1/ G/1
> > > (XEN) [2015-06-25 10:46:31.820]  MSI-X   87 vec=c2 lowest  edge   
> > > assert  log
> > lowest dest=00000002 mask=1/ G/1
> > > (XEN) [2015-06-25 10:46:31.820]  MSI-X   88 vec=ca lowest  edge   
> > > assert  log
> > lowest dest=00000002 mask=1/ G/1
> >
> > > I.e. they didn't get unmasked by the guest.
> Attached a first debugging patch.
>
> Jan
Hi Jan,

Strange, i don't see *any* of your printk's being hit ... (xl dmesg 
attached).
(What i do notice is that it looks like he xhci controller is 
initialized early by seabios instead of the guest kernel, but it that 
should also be true in the "working case" since the seabios version 
didn't change.)
--
Sander

Attachment: xl-dmesg.txt
Description: Text document

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