From: Alex Williamson <alex.williamson@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Chris Wright <chrisw@sous-sol.org>,
Arnd Hannemann <arnd@arndnet.de>,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: Re: 3.2rc1: bootup fails: DRHD: handling fault status reg 2
Date: Tue, 15 Nov 2011 21:01:23 -0700 [thread overview]
Message-ID: <1321416083.26410.8.camel@bling.home> (raw)
In-Reply-To: <1321347330.1932.65.camel@shinybook.infradead.org>
On Tue, 2011-11-15 at 08:55 +0000, David Woodhouse wrote:
> On Mon, 2011-11-14 at 20:36 -0800, Chris Wright wrote:
> > As for the endless loop of DMAR faults...sounds like the Ricoh
> > cardbus/firewire issue where the firewire fucntion does DMA from
> > function 0. I thought this was quirked and fixed though.
>
> Alex? You were handling this as part of the IOMMU 'group' functionality,
> weren't you? Did you have a test machine... you do now :)
The group functionality is primarily for iommu_ops so we can expose to
users which devices need to be grouped because of iommu restrictions.
We can add a quirk to the grouping for this device, but then we have to
figure out how dma_ops makes use of that info too. Maybe we could have
a 'struct pci_dev *pci_get_iommu_alias_quirk(struct pci_dev *pdev)'
function that given device 0d:00.3 would return 0d:00.0 for this case
and both get_domain_for_dev() and intel_iommu_device_group() could make
use of it. Thanks,
Alex
prev parent reply other threads:[~2011-11-16 4:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 22:33 Arnd Hannemann
2011-11-15 0:53 ` Arnd Hannemann
2011-11-15 4:31 ` Robert Hancock
2011-11-15 6:29 ` Arnd Hannemann
2011-11-15 4:36 ` Chris Wright
2011-11-15 6:34 ` Arnd Hannemann
2011-11-15 8:55 ` David Woodhouse
2011-11-16 4:01 ` Alex Williamson [this message]
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=1321416083.26410.8.camel@bling.home \
--to=alex.williamson@redhat.com \
--cc=arnd@arndnet.de \
--cc=chrisw@sous-sol.org \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®