[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080627171201.GC26130@il.ibm.com>
Date: Fri, 27 Jun 2008 13:12:01 -0400
From: Muli Ben-Yehuda <muli@...ibm.com>
To: Joerg Roedel <joro@...tes.org>
Cc: Andi Kleen <andi@...stfloor.org>, Adrian Bunk <bunk@...nel.org>,
Joerg Roedel <joerg.roedel@....com>, tglx@...utronix.de,
mingo@...hat.com, linux-kernel@...r.kernel.org,
iommu@...ts.linux-foundation.org, bhavna.sarathy@....com,
Sebastian.Biemueller@....com, robert.richter@....com
Subject: Re: [PATCH 01/34] AMD IOMMU: add Kconfig entry
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists