[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v3 0/3] x86/IOMMU: multi-vector MSI prerequisites

>>> On 13.04.13 at 03:16, Suravee Suthikulpanit <suravee.suthikulpanit@xxxxxxx> 
>>> wrote:
> On 4/12/2013 5:18 AM, Jan Beulich wrote:
>> 1: IOMMU: allow MSI message to IRTE propagation to fail
>> 2: AMD IOMMU: allocate IRTE entries instead of using a static mapping
>> 3: AMD IOMMU: untie remap and vector maps
>> See the individual patches for what, if anything, has changed from v2.
>> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
> This patch setfix the previous issue we sawfrom the get_intremap_entry() 
> causing the ASSERT on (table != NULL).  Now the system is booting.
> However, I think there are some issues with the interrupt remapping for 
> the USBdevices. During dom0 booting, it gave error w/ regarding timeout 
> during loadingsome USB drivers. Also, lsmodis showing "hid_generic" 
> module is missing. This resulting in the USBmouse and keyboard are not 
> working.

So I would guess something must be wrong with the IO-APIC
related code paths then. I just went through them again, but the
only thing I spotted was a pointless duplicate assignment to
ioapic_sbdf[].pin_2_idx[] in amd_iommu_setup_ioapic_remapping().
Sadly we don't have the 'V' debug key for AMD yet, otherwise the
combination of 'V' and 'z' output would likely tell us quite clearly
what's wrong. Looking at 'z' might still be worthwhile though...



Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.