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

Re: [Xen-devel] [PATCH 1/2 v5] iommu/amd: Fix logic for clearing the IOMMU interrupt bits

>>> On 13.06.13 at 18:34, Suravee Suthikulanit <suravee.suthikulpanit@xxxxxxx> 
>>> wrote:
> Basically, the only different is this line that only appears in the "Bad" 
> version.
>      (XEN)  MSI     56 vec=28  fixed  edge deassert phys    cpu dest=00000001 
> mask=0/0/1
> "xl debug-key i" also show the following information
>      (XEN)    IRQ:  56 affinity:1 vec:28 type=AMD-IOMMU-MSI   status=00000000 
> mapped, unbound

There are several questionable things here:
- the interrupt being of "deassert" kind
- destination mode being physical (while all others are logical)
- the interrupt being unbound (i.e. there's no action associated
  with it, and hence no handler would ever get called)

> Not sure what "status=0" means.

This says that none of the IRQ_* flags are set in desc->status,
which isn't in itself problematic for non-guest interrupts.


Xen-devel mailing list



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