linux-kernel - Re: 3.2rc1: bootup fails: DRHD: handling fault status reg 2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 15 Nov 2011 21:01:23 -0700
From:	Alex Williamson <alex.williamson@...hat.com>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	Chris Wright <chrisw@...s-sol.org>,
	Arnd Hannemann <arnd@...dnet.de>, linux-kernel@...r.kernel.org,
	iommu@...ts.linux-foundation.org
Subject: Re: 3.2rc1: bootup fails: DRHD: handling fault status reg 2

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/