From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: iommu external module Date: Thu, 02 Oct 2008 18:30:47 +0300 Message-ID: <48E4E927.6070801@redhat.com> References: <48E4C26D.6030608@redhat.com> <20081002145845.GB6909@il.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: KVM list To: Muli Ben-Yehuda Return-path: Received: from mx2.redhat.com ([66.187.237.31]:44192 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752579AbYJBPdR (ORCPT ); Thu, 2 Oct 2008 11:33:17 -0400 In-Reply-To: <20081002145845.GB6909@il.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: Muli Ben-Yehuda wrote: > On Thu, Oct 02, 2008 at 03:45:33PM +0300, Avi Kivity wrote: > > >> We can fix this fairly simply by having an external module for the >> iommus, much like kvm itself. I don't think it should be too >> difficult, and it will provide a lot of testing to us, and important >> functionality for our users. >> > > The problem is that if we want to enable DMA translation for a given > device, we have to do it before it has any outstanding DMAs. As long > as you have a device that you want to enable translation for as > built-in, you'll need the IOMMU built-in as well, or will need to > reset the device when you load the IOMMU. That's why all IOMMUs are > currently built-in. > This is for using with kvm as an external module, so there is no question of a built in device. It's purely for older kernels; I'm not calling for modular iommus. -- error compiling committee.c: too many arguments to function