From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:58277) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UhgQJ-0004qt-JV for qemu-devel@nongnu.org; Wed, 29 May 2013 09:28:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UhgQI-00077X-7m for qemu-devel@nongnu.org; Wed, 29 May 2013 09:28:15 -0400 Received: from plane.gmane.org ([80.91.229.3]:56247) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UhgIO-0004AH-HK for qemu-devel@nongnu.org; Wed, 29 May 2013 09:20:04 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UhgIN-00064V-1E for qemu-devel@nongnu.org; Wed, 29 May 2013 15:20:03 +0200 Received: from august.inf.tu-dresden.de ([141.76.48.124]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 29 May 2013 15:20:03 +0200 Received: from jsteckli by august.inf.tu-dresden.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 29 May 2013 15:20:03 +0200 From: Julian Stecklina Date: Wed, 29 May 2013 14:32:50 +0200 Message-ID: References: <20130527093409.GH21969@stefanha-thinkpad.redhat.com> <51A496C4.1020602@os.inf.tu-dresden.de> <87r4grca4p.fsf@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit In-Reply-To: <87r4grca4p.fsf@codemonkey.ws> Subject: Re: [Qemu-devel] snabbswitch integration with QEMU for userspace ethernet I/O List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On 05/28/2013 07:00 PM, Anthony Liguori wrote: > We aren't going to support any interface that enables out of tree > devices. This is just plugins in a different form with even more > downsides. You cannot easily keep track of dirty info, the guest > physical address translation to host is difficult to keep in sync > (imagine the complexity of memory hotplug). Is there a document describing the current qemu VM migration process, especially the dirty page tracking, except the code? As a side note: The downsides of a naive approach are about that of PCI passtrough devices with the opportunity to fix them later on. That being said, I can live with this not being included in mainline qemu. Julian