From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Wei Wang2 <wei.wang2@amd.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Allen Kay <allen.m.kay@intel.com>,
Tim Deegan <Tim.Deegan@citrix.com>,
Jean Guyader <Jean.Guyader@citrix.com>
Subject: Re: Re: IOMMU faults
Date: Thu, 16 Jun 2011 10:47:30 -0400 [thread overview]
Message-ID: <20110616144730.GA6108@dumpdata.com> (raw)
In-Reply-To: <201106161630.15290.wei.wang2@amd.com>
> > 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 off?
Perhaps similar to the PCIe AER handling?
next prev parent reply other threads:[~2011-06-16 14:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 9:25 IOMMU faults Tim Deegan
2011-06-16 9:47 ` Jean Guyader
2011-06-16 10:07 ` Tim Deegan
2011-06-16 10:28 ` Jean Guyader
2011-06-24 13:32 ` Tim Deegan
2011-06-30 10:08 ` Tim Deegan
2011-06-30 10:31 ` Jean Guyader
2011-06-16 14:30 ` Wei Wang2
2011-06-16 14:47 ` Konrad Rzeszutek Wilk [this message]
2011-06-17 8:08 ` Tim Deegan
2011-06-16 19:21 ` Kay, Allen M
2011-06-17 8:06 ` Tim Deegan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110616144730.GA6108@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Jean.Guyader@citrix.com \
--cc=Tim.Deegan@citrix.com \
--cc=allen.m.kay@intel.com \
--cc=wei.wang2@amd.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.