From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NrA5I-0004Et-Ja for qemu-devel@nongnu.org; Mon, 15 Mar 2010 09:11:52 -0400 Received: from [199.232.76.173] (port=36448 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NrA5I-0004EY-8o for qemu-devel@nongnu.org; Mon, 15 Mar 2010 09:11:52 -0400 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1NrA5H-0006v4-K6 for qemu-devel@nongnu.org; Mon, 15 Mar 2010 09:11:52 -0400 Received: from mx1.redhat.com ([209.132.183.28]:28238) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NrA5H-0006us-8G for qemu-devel@nongnu.org; Mon, 15 Mar 2010 09:11:51 -0400 Message-ID: <4B9E320E.7040605@redhat.com> Date: Mon, 15 Mar 2010 15:11:42 +0200 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Ideas wiki for GSoC 2010 References: <20100310183023.6632aece@redhat.com> <4B9E2745.7060903@redhat.com> <20100315125313.GK9457@il.ibm.com> <20100315130310.GE13108@8bytes.org> In-Reply-To: <20100315130310.GE13108@8bytes.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Joerg Roedel Cc: Muli Ben-Yehuda , agraf@suse.de, aliguori@us.ibm.com, kvm@vger.kernel.org, jan.kiszka@siemens.com, qemu-devel@nongnu.org, Luiz Capitulino , agl@us.ibm.com, Nadav Amit , Ben-Ami Yassour1 On 03/15/2010 03:03 PM, Joerg Roedel wrote: > >>> I will add another project - iommu emulation. Could be very useful >>> for doing device assignment to nested guests, which could make >>> testing a lot easier. >>> >> Our experiments show that nested device assignment is pretty much >> required for I/O performance in nested scenarios. >> > Really? I did a small test with virtio-blk in a nested guest (disk read > with dd, so not a real benchmark) and got a reasonable read-performance > of around 25MB/s from the disk in the l2-guest. > > Your guest wasn't doing a zillion VMREADs and VMWRITEs every exit. I plan to reduce VMREAD/VMWRITE overhead for kvm, but not much we can do for other guests. -- error compiling committee.c: too many arguments to function