Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1423830AbbFEOfe (ORCPT ); Fri, 5 Jun 2015 10:35:34 -0400 Received: from cantor2.suse.de ([195.135.220.15]:56320 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964772AbbFEOfb (ORCPT ); Fri, 5 Jun 2015 10:35:31 -0400 Date: Fri, 5 Jun 2015 16:35:28 +0200 From: "jroedel@suse.de" To: Will Deacon Cc: Joerg Roedel , "iommu@lists.linux-foundation.org" , Kukjin Kim , David Woodhouse , Heiko Stuebner , Hiroshi Doyu , Thierry Reding , Alex Williamson , Robin Murphy , Laurent Pinchart , Oded Gabbay , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH 00/22 v2] Introduce default domains for iommu groups Message-ID: <20150605143528.GK16345@suse.de> References: <1432831305-11126-1-git-send-email-joro@8bytes.org> <20150605142206.GB7420@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150605142206.GB7420@arm.com> 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: 1444 Lines: 36 Hi Will, Thanks for having a look! On Fri, Jun 05, 2015 at 03:22:06PM +0100, Will Deacon wrote: > > Most of this looks fine to me, modulo by comments about the dm regions > (which I'm not sure how to implement for ARM). When there are no direct mapping requirements from the firmware on ARM, you can just return an empty list in these call-backs. > > A major change is that now the default domain has to be > > allocated by the code that allocates the iommu group. For > > PCI devices this happens in the IOMMU core, but drivers > > allocating the group on their own can now implement a policy > > that fits their needs (e.g. not allocate one domain per > > group but let multiple groups share one domain). > > Makes sense. I really think we should be moving group allocation out of > the IOMMU drivers and into the bus code, like we already have for PCI. > Once we've got a way to describe groups of platform devices (e.g. in the > device-tree), then we can have the group creation happen automatically > as part of Laurent's of_iommu work. Yes, that makes sense. And PCI is pretty hardcoded into the iommu-groups implementation right now. This needs probably be more generic too. Joerg -- 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/