[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1319231795.19108.22.camel@bling.home>
Date: Fri, 21 Oct 2011 15:16:34 -0600
From: Alex Williamson <alex.williamson@...hat.com>
To: "Woodhouse, David" <david.woodhouse@...el.com>
Cc: "joerg.roedel@....com" <joerg.roedel@....com>,
"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"chrisw@...hat.com" <chrisw@...hat.com>,
"agraf@...e.de" <agraf@...e.de>,
"dwg@....ibm.com" <dwg@....ibm.com>,
"scottwood@...escale.com" <scottwood@...escale.com>,
"B08248@...escale.com" <B08248@...escale.com>,
"benh@...nel.crashing.org" <benh@...nel.crashing.org>
Subject: Re: [PATCH 0/4] iommu: iommu_ops group interface
On Fri, 2011-10-21 at 20:34 +0000, Woodhouse, David wrote:
> On Fri, 2011-10-21 at 13:55 -0600, Alex Williamson wrote:
> > IOMMUs can't always distiguish transactions from each individual
> > device in a system. Sometimes this is by design (such as powerpc
> > partitionable endpoints), other times by topology (PCIe-to-PCI
> > bridges masking downstream devices). We call these sets of
> > indistinguishable devices "groups".
>
> Other times it's because a multi-function PCIe device is broken and does
> all its DMA from function zero.... like some Ricoh devices seen in
> laptops. Can you handle quirks to "group" those too?
I could add:
drivers/pci/quirks.c: int pci_iommu_group_mf_quirk(struct pci_dev *)
That's used just like iommu_group_mf to always blacklist specific
devices. Let me know VID/DID if you have them. 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/
Powered by blists - more mailing lists