From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC] KVM: Balloon support for device assignment Date: Wed, 17 Feb 2010 12:27:09 +0200 Message-ID: <4B7BC47D.4030808@redhat.com> References: <1266399807-4498-1-git-send-email-borove@il.ibm.com> <1266399807-4498-2-git-send-email-borove@il.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, benami@il.ibm.com, Gerd Hoffmann To: borove@il.ibm.com Return-path: Received: from mx1.redhat.com ([209.132.183.28]:24953 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751382Ab0BQK1O (ORCPT ); Wed, 17 Feb 2010 05:27:14 -0500 In-Reply-To: <1266399807-4498-2-git-send-email-borove@il.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: On 02/17/2010 11:43 AM, borove@il.ibm.com wrote: > From: Eran Borovik > > This patch adds modifications to allow correct > balloon operation when a virtual guest uses a direct assigned device. > The modifications include a new interface between qemu and kvm to allow > mapping and unmapping the pages from the IOMMU as well as pinning and unpinning as needed. > The plan for iommu support is to push it into uio. Instead of kvm managing the iommu directly, I'd like qemu to open a uio device and set up an iommu mapping there, which will just happen to match the kvm memory slots. Similarly, interrupts will be forwarded using irqfds. This will allow using the iommu without kvm, and reduce the amount of special purpose kvm code. These patches make the transition more difficult which worries me. I know Gerd looked at making the move, but no longer. -- error compiling committee.c: too many arguments to function