From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from ch1ehsobe001.messaging.microsoft.com ([216.32.181.181]:34803 "EHLO CH1EHSOBE001.bigfish.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752287Ab1FFPfl (ORCPT ); Mon, 6 Jun 2011 11:35:41 -0400 Date: Mon, 6 Jun 2011 17:35:57 +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: <20110606153557.GE1953@amd.com> References: <1307053663-24572-1-git-send-email-ohad@wizery.com> <20110606100950.GC30762@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: List-ID: Sender: On Mon, Jun 06, 2011 at 11:15:30AM -0400, Ohad Ben-Cohen wrote: > This is insufficient; users need somehow to tell what page sizes are > supported by the underlying hardware (we can't assume host page-sizes, > and we want to use bigger pages whenever possible, to relax the TLB > pressure). / What does the IOMMU-API user need this info for? On the x86 IOMMUs these details are handled transparently by the IOMMU driver. 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