From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joerg Roedel Subject: Re: [PATCH] [RESEND] VT-d: Support multiple device assignment to one guest Date: Wed, 29 Oct 2008 11:25:28 +0100 Message-ID: <20081029102528.GD6345@amd.com> References: <0122C7C995D32147B66BF4F440D3016301CF9679@pdsmsx415.ccr.corp.intel.com> <48EB6431.4070300@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: "Han, Weidong" , kvm@vger.kernel.org, Amit Shah , "Kay, Allen M" , "Yang, Sheng" , benami@il.ibm.com, muli@il.ibm.com To: Avi Kivity Return-path: Received: from outbound-wa4.frontbridge.com ([216.32.181.16]:37489 "EHLO WA4EHSOBE006.bigfish.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752019AbYJ2K0D (ORCPT ); Wed, 29 Oct 2008 06:26:03 -0400 Content-Disposition: inline In-Reply-To: <48EB6431.4070300@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: (sorry for joining this late, I returned from a 3-week vacation this monday) On Tue, Oct 07, 2008 at 03:29:21PM +0200, Avi Kivity wrote: > Oh, I see it now. Different devices may need to go under different iommus. > > This really feels like it should be handled by the iommu API. Users > shouldn't need to bother with it. > > Joerg, can your dma api handle this? Yes. The API works in terms of devices and domains. The fact that a domain may contain devices behind different IOMMUs is hidden to the user of that API. Joerg -- | AMD Saxony Limited Liability Company & Co. KG Operating | Wilschdorfer Landstr. 101, 01109 Dresden, Germany System | Register Court Dresden: HRA 4896 Research | General Partner authorized to represent: Center | AMD Saxony LLC (Wilmington, Delaware, US) | General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy