From mboxrd@z Thu Jan 1 00:00:00 1970 From: 'Joerg Roedel' Subject: Re: [PATCH 0/17] [v4] Support VT-d multiple device assignment for KVM Date: Mon, 8 Dec 2008 21:18:04 +0100 Message-ID: <20081208201803.GC18346@8bytes.org> References: <715D42877B251141A38726ABF5CABF2C018BF4DC9F@pdsmsx503.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Woodhouse, David" , 'Jesse Barnes' , 'Avi Kivity' , "Kay, Allen M" , "Yu, Fenghua" , 'Mark McLoughlin' , "'kvm@vger.kernel.org'" , "'iommu@lists.linux-foundation.org'" To: "Han, Weidong" Return-path: Received: from 8bytes.org ([88.198.83.132]:50854 "EHLO 8bytes.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751892AbYLHUSG (ORCPT ); Mon, 8 Dec 2008 15:18:06 -0500 Content-Disposition: inline In-Reply-To: <715D42877B251141A38726ABF5CABF2C018BF4DC9F@pdsmsx503.ccr.corp.intel.com> Sender: kvm-owner@vger.kernel.org List-ID: Great. I rebased the IOMMU API and AMD IOMMU support patches and pushed them out to kernel.org. I will also do a post of them. On Tue, Dec 09, 2008 at 12:01:52AM +0800, Han, Weidong wrote: > This patchset supports VT-d multiple device assignment for KVM. > > Main changes from V3 to V4: > - rebase intel iommu patches to dave's iommu-2.6 tree, KVM patches are still based on avi/master tree > - fix a potential infinite loop in vm_domain_remove_one_dev_info > - add a spin lock to protect iommu setting in domain > - fix most of comments from Mark, but some comments are not adopted. I still use iommu bitmap, because it's simple, and iommu list is not more complex to implement. Additionally, I still separate some functions for virtual machine domain, because i think mixing many flag judgments in common functions makes things complex, and hard to maintain. > - On KVM side, assign device in kvm_free_assigned_device, because In kvm_iommu_unmap_memslots(), assigned_dev_head is already empty. > > > Regards, > Weidong