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

Re: [Xen-devel] [PATCH 1/6] AMD IOMMU: allocate IRTE entries instead of using a static mapping

On 04/24/2013 08:34 AM, Jan Beulich wrote:
On 23.04.13 at 17:06, Suravee Suthikulanit <suravee.suthikulpanit@xxxxxxx> 
On 4/23/2013 8:21 AM, Suravee Suthikulanit wrote:
I am now reproducing the issue with the USB devices not working with
this patch again.  I'll continue to investigate more.

Ok, I have more update on the issue.  Bellow, I include the output from
"xl debug-key i".  It is showing several IRQ having the same vector "b0".
This is not the case when booting with the xen w/o the patch.
Right, and I spotted a bug in the respective code, but I can't
readily connect that bug to the behavior you observed (i.e. I
can't explain why the bad vector would be the same all the time).

Nevertheless, attached a fixed version of the first patch of
the most recent series - let's see how much of a difference this



I have finally root cause the issue.  Here are the two patches that should help 
fixing the issue.
The first patch fixes the issue with the mouse/keyboard not working while the 
second patch
add a debug-key to help dumping the IRTE which I used to debug the issue.

I have also include the xl dmesg from both "before" patching and "after" 
applying patch 1, 2 and the fixes.
These also include the output from debug keys "M,z,i,j"


Attachment: after.txt
Description: after.txt

Attachment: before.txt
Description: before.txt

Attachment: 0001-Fix-IOAPIC-interrupt-routing-issue-introduced-in-the.patch
Description: 0001-Fix-IOAPIC-interrupt-routing-issue-introduced-in-the.patch

Attachment: 0002-Add-debug-key-for-dumping-IOMMU-IRTE.patch
Description: 0002-Add-debug-key-for-dumping-IOMMU-IRTE.patch

Xen-devel mailing list



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