From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [RFC] [VTD][patch 2/3] vt-d support for pci passthrough: kvm-vtd-user.patch Date: Tue, 06 May 2008 19:39:50 -0500 Message-ID: <4820FA56.8000200@codemonkey.ws> References: <1FE6DD409037234FAB833C420AA843EC01438CB5@orsmsx424.amr.corp.intel.com> <482034C0.90808@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Chris Wright , kvm-devel@lists.sourceforge.net, "Kay, Allen M" , Ben-Ami Yassour1 To: Avi Kivity Return-path: In-Reply-To: <482034C0.90808@qumranet.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org Avi Kivity wrote: > Kay, Allen M wrote: > >> Still todo: move vt.d to kvm-intel.ko module. >> >> > > Not sure it's the right thing to do. If we get the iommus abstracted > properly, we can rename vtd.c to dma.c and move it to virt/kvm/. > > The code is certainly a lot more about managing memory than anything vmx > specific. It's hardly x86 specific, even. > Really, an external interface to KVM that allowed someone to query the GPA => PA mapping would suffice. It should not fault in pages that aren't present and we should provide notifications for when the mapping changes for a given reason. Userspace can enforce the requirement that memory remains present via mlock(). This allows us to implement a PV API for DMA registration without the IOMMU code having any particular knowledge of it. Regards, Anthony Liguori ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone