This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: IOMMU faults

To: Wei Wang2 <wei.wang2@xxxxxxx>
Subject: Re: [Xen-devel] Re: IOMMU faults
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Thu, 16 Jun 2011 10:47:30 -0400
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Allen Kay <allen.m.kay@xxxxxxxxx>, Tim Deegan <Tim.Deegan@xxxxxxxxxx>, Jean Guyader <Jean.Guyader@xxxxxxxxxx>
Delivery-date: Thu, 16 Jun 2011 07:48:18 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <201106161630.15290.wei.wang2@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20110616092509.GH17634@xxxxxxxxxxxxxxxxxxxxxxx> <201106161630.15290.wei.wang2@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
> > I was considering just writing 0 to the faulting card's PCI command
> > register, but I'm told that's not always enough to properly deactivate
> > a card, and it might be a little over-zealous to do it on the first
> > offence.
> > Ideas?
> It seems difficult to find a generic approach to stop a device without 
> knowing 
> more device specific details... 

Perhaps make something similar to the MCE fault interrupts? As in when the error
happens, the Dom0 is notified of the offending BDF and persuses whatever action
it thinks are neccessary. The action would be to tell the device driver to
turn itself off. But how it would interact with the driver.. Well how does Linux
deal with this today? Is there an extension to the device driver API (similar to
the power) to notify the driver that it has done bad things and to shut itself 

Perhaps similar to the PCIe AER handling?

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>