Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751956Ab1FGHwH (ORCPT ); Tue, 7 Jun 2011 03:52:07 -0400 Received: from tx2ehsobe002.messaging.microsoft.com ([65.55.88.12]:1190 "EHLO TX2EHSOBE003.bigfish.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751647Ab1FGHwE (ORCPT ); Tue, 7 Jun 2011 03:52:04 -0400 X-SpamScore: -16 X-BigFish: VPS-16(z1039oz9371M1432N98dKzz1202hzz15d4R8275bhz32i668h839h62h) X-Spam-TCS-SCL: 1:0 X-Forefront-Antispam-Report: CIP:163.181.249.108;KIP:(null);UIP:(null);IPVD:NLI;H:ausb3twp01.amd.com;RD:none;EFVD:NLI X-WSS-ID: 0LMETUN-01-9HV-02 X-M-MSG: Date: Tue, 7 Jun 2011 09:52:21 +0200 From: "Roedel, Joerg" To: Ohad Ben-Cohen CC: "linux-media@vger.kernel.org" , "linux-omap@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "laurent.pinchart@ideasonboard.com" , "Hiroshi.DOYU@nokia.com" , "arnd@arndb.de" , "davidb@codeaurora.org" , Omar Ramirez Luna Subject: Re: [RFC 0/6] iommu: generic api migration and grouping Message-ID: <20110607075221.GB4407@amd.com> References: <1307053663-24572-1-git-send-email-ohad@wizery.com> <20110606100950.GC30762@amd.com> <20110606153557.GE1953@amd.com> <20110606192030.GA4356@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-OriginatorOrg: amd.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1271 Lines: 33 On Mon, Jun 06, 2011 at 04:09:33PM -0400, Ohad Ben-Cohen wrote: > On Mon, Jun 6, 2011 at 10:20 PM, Roedel, Joerg wrote: > > Well, it certainly makes sense to have a single implementation for this. > > But I want to hide this complexity to the user of the IOMMU-API. The > > best choice is to put this into the layer between the IOMMU-API and the > > backend implementation. > > I agree. > > The IOMMU API should take physically contiguous regions from the user, > split them up according to page-sizes (/alignment requirements) > supported by the hardware, and then tell the underlying implementation > what to map where. Yup. Btw, is there any IOMMU hardware which supports non-natural alignment? In this case we need to expose these requirements somehow. Regards, Joerg -- AMD Operating System Research Center Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach General Managers: Alberto Bozzo, Andrew Bowd Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632 -- 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/