From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:55925) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UhimY-0007n8-DI for qemu-devel@nongnu.org; Wed, 29 May 2013 11:59:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UhimS-0004RR-Ti for qemu-devel@nongnu.org; Wed, 29 May 2013 11:59:22 -0400 Received: from os.inf.tu-dresden.de ([2002:8d4c:3001:48::99]:49387) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UhimS-0004RD-Ma for qemu-devel@nongnu.org; Wed, 29 May 2013 11:59:16 -0400 Message-ID: <51A625D1.5020900@os.inf.tu-dresden.de> Date: Wed, 29 May 2013 17:59:13 +0200 From: Julian Stecklina MIME-Version: 1.0 References: <20130527093409.GH21969@stefanha-thinkpad.redhat.com> <51A496C4.1020602@os.inf.tu-dresden.de> <87r4grca4p.fsf@codemonkey.ws> <20130529143156.GA9564@stefanha-thinkpad.redhat.com> In-Reply-To: <20130529143156.GA9564@stefanha-thinkpad.redhat.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2LQJVSQUPAKIBMFJQPPVX" 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: Stefan Hajnoczi Cc: qemu-devel@nongnu.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2LQJVSQUPAKIBMFJQPPVX Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 05/29/2013 04:31 PM, Stefan Hajnoczi wrote: > On Wed, May 29, 2013 at 02:32:50PM +0200, Julian Stecklina wrote: >> 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 PC= I >> passtrough devices with the opportunity to fix them later on. That bei= ng >> said, I can live with this not being included in mainline qemu. >=20 > Asking for documentation and in the next paragraph stating you don't > mind keeping patches out-of-tree... >=20 > The QEMU community exists because people are willing to contribute. If= > you intend to only "take" and not "give", then you'll find that people > gradually stop responding to your emails. I am not saying that this will be closed in any way. I'll create a github repo once I have to show something. If there is interest in getting this into mainline qemu, then why not. Currently, it seems that there is a categorical rejection of such functionality. But this discussion is moot until there is working code. ;) Julian ------enig2LQJVSQUPAKIBMFJQPPVX Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) iEYEARECAAYFAlGmJdEACgkQ2EtjUdW3H9nQGgCgjxQAP1kHBMHyBltQyPb9z99A eVwAoJaAnVzMRuGMN2agpbGjU7WXp+bf =JFJ0 -----END PGP SIGNATURE----- ------enig2LQJVSQUPAKIBMFJQPPVX--