[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1336780681.12477.198.camel@bling.home>
Date: Fri, 11 May 2012 17:58:01 -0600
From: Alex Williamson <alex.williamson@...hat.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: benh@...nel.crashing.org, aik@...abs.ru,
david@...son.dropbear.id.au, joerg.roedel@....com,
dwmw2@...radead.org, chrisw@...s-sol.org, agraf@...e.de,
benve@...co.com, aafabbri@...co.com, B08248@...escale.com,
B07421@...escale.com, avi@...hat.com, konrad.wilk@...cle.com,
kvm@...r.kernel.org, qemu-devel@...gnu.org,
iommu@...ts.linux-foundation.org, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org, bhelgaas@...gle.com
Subject: Re: [PATCH 01/13] driver core: Add iommu_group tracking to struct
device
On Fri, 2012-05-11 at 16:38 -0700, Greg KH wrote:
> On Fri, May 11, 2012 at 04:55:35PM -0600, Alex Williamson wrote:
> > IOMMU groups allow IOMMU drivers to represent DMA visibility
> > and isolation of devices. Multiple devices may be grouped
> > together for the purposes of DMA. Placing a pointer on
> > struct device enable easy access for things like streaming
> > DMA programming and drivers like VFIO.
> >
> > Signed-off-by: Alex Williamson <alex.williamson@...hat.com>
>
> Can't you get this today from the iommu_ops pointer that is on the bus
> that the device is associated with? Or can devices on a bus have
> different iommu_group pointers?
The latter, each device on a bus might be it's own group. This is often
the case on x86 unless PCIe-to-PCI bridges obscure the device
visibility. 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