Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761630AbYF0RM4 (ORCPT ); Fri, 27 Jun 2008 13:12:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759548AbYF0RMZ (ORCPT ); Fri, 27 Jun 2008 13:12:25 -0400 Received: from mtagate3.uk.ibm.com ([195.212.29.136]:2101 "EHLO mtagate3.uk.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758744AbYF0RMY (ORCPT ); Fri, 27 Jun 2008 13:12:24 -0400 Date: Fri, 27 Jun 2008 13:12:01 -0400 From: Muli Ben-Yehuda To: Joerg Roedel Cc: Andi Kleen , Adrian Bunk , Joerg Roedel , tglx@linutronix.de, mingo@redhat.com, linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org, bhavna.sarathy@amd.com, Sebastian.Biemueller@amd.com, robert.richter@amd.com Subject: Re: [PATCH 01/34] AMD IOMMU: add Kconfig entry Message-ID: <20080627171201.GC26130@il.ibm.com> References: <1214508490-29683-1-git-send-email-joerg.roedel@amd.com> <1214508490-29683-2-git-send-email-joerg.roedel@amd.com> <20080627142558.GG18644@cs181140183.pp.htv.fi> <878wwrq6im.fsf@basil.nowhere.org> <20080627163945.GA26130@il.ibm.com> <20080627165430.GD10197@8bytes.org> <20080627165947.GB26130@il.ibm.com> <20080627170546.GE10197@8bytes.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080627170546.GE10197@8bytes.org> User-Agent: Mutt/1.5.15+20070412 (2007-04-11) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1265 Lines: 36 On Fri, Jun 27, 2008 at 07:05:46PM +0200, Joerg Roedel wrote: > On Fri, Jun 27, 2008 at 12:59:47PM -0400, Muli Ben-Yehuda wrote: > > On Fri, Jun 27, 2008 at 06:54:30PM +0200, Joerg Roedel wrote: > > > > > True. At least for the case without device isolation I have some > > > optimizations in mind which will minimize the performance > > > tradeoff. I hope to have them ready for 2.6.28 :) > > > > Do you mean the case where you have a single I/O address space which > > is shared by all devices? > > Yes. I think this will be the case used most when IOMMU is used for > virtualization Could you elaborate on what you mean here? I assume you're thinking one I/O address space for the host, and one I/O address space per guest with assigned devices? > and to handle devices with limited DMA address ranges. I'd be pretty surprised if you'll find such devices on machines which will have AMD's IOMMU... > In this case there is a lot to optimize. Looking forward to seeing what you have in mind :-) Cheers, Muli -- 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/