Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761389Ab2ELAAs (ORCPT ); Fri, 11 May 2012 20:00:48 -0400 Received: from mail-pb0-f46.google.com ([209.85.160.46]:40107 "EHLO mail-pb0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761323Ab2ELAAp (ORCPT ); Fri, 11 May 2012 20:00:45 -0400 Date: Fri, 11 May 2012 17:00:40 -0700 From: Greg KH To: Alex Williamson Cc: benh@kernel.crashing.org, aik@ozlabs.ru, david@gibson.dropbear.id.au, joerg.roedel@amd.com, dwmw2@infradead.org, chrisw@sous-sol.org, agraf@suse.de, benve@cisco.com, aafabbri@cisco.com, B08248@freescale.com, B07421@freescale.com, avi@redhat.com, konrad.wilk@oracle.com, kvm@vger.kernel.org, qemu-devel@nongnu.org, iommu@lists.linux-foundation.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, bhelgaas@google.com Subject: Re: [PATCH 01/13] driver core: Add iommu_group tracking to struct device Message-ID: <20120512000040.GA17559@kroah.com> References: <20120511222148.30496.68571.stgit@bling.home> <20120511225534.30496.54563.stgit@bling.home> <20120511233821.GA9335@kroah.com> <1336780681.12477.198.camel@bling.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1336780681.12477.198.camel@bling.home> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1283 Lines: 28 On Fri, May 11, 2012 at 05:58:01PM -0600, Alex Williamson wrote: > 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 > > > > 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, Ah, ok, then I have no objection to add this to struct device: Acked-by: Greg Kroah-Hartman -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/