From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:43307) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rj8p1-00083s-Qw for qemu-devel@nongnu.org; Fri, 06 Jan 2012 07:23:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rj8p0-0005TM-GP for qemu-devel@nongnu.org; Fri, 06 Jan 2012 07:22:59 -0500 Received: from fmmailgate01.web.de ([217.72.192.221]:48367) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rj8p0-0005TC-70 for qemu-devel@nongnu.org; Fri, 06 Jan 2012 07:22:58 -0500 Received: from moweb001.kundenserver.de (moweb001.kundenserver.de [172.19.20.114]) by fmmailgate01.web.de (Postfix) with ESMTP id E87411A86DE37 for ; Fri, 6 Jan 2012 13:22:56 +0100 (CET) Message-ID: <4F06E789.6050509@web.de> Date: Fri, 06 Jan 2012 10:22:33 -0200 From: Jan Kiszka MIME-Version: 1.0 References: <1323467645-24271-1-git-send-email-anthony.perard@citrix.com> <1323467645-24271-6-git-send-email-anthony.perard@citrix.com> <4EE3382D.80903@web.de> <4EE609BF.1070307@siemens.com> <4EE617BA.4030102@siemens.com> <4EEE25DA.2080400@redhat.com> <4F048B10.1060505@redhat.com> <4F059C8C.2030303@redhat.com> <4F05A684.7000509@redhat.com> <4F05BF9E.7000203@redhat.com> <4F05D0BC.70707@redhat.com> <4F05E301.2020808@redhat.com> <4F05F09E.8030800@web.de> <4F06E6C6.5080607@redhat.com> In-Reply-To: <4F06E6C6.5080607@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA286793C49D7C06177BA9609" Subject: Re: [Qemu-devel] [PATCH V2 5/5] vga-cirrus: Workaround during restore when using Xen. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Anthony Perard , Xen Devel , QEMU-devel , Stefano Stabellini This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA286793C49D7C06177BA9609 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2012-01-06 10:19, Avi Kivity wrote: > On 01/05/2012 08:49 PM, Jan Kiszka wrote: >> To me this still sounds like a cirrus-only xen workaround that >> nevertheless spreads widely. >=20 > It is. >=20 >> Again, what speaks against migrating the information Xen needs before >> creating the machine or a single device? That would only introduce a >> generic concept of an (optional) "early", let's call it >> "accelerator-related" vmstate and would allow Xen to deal with all the= >> specifics behind the curtain. >> >=20 > Adding more concepts, just to work around a bug (and this is really a > bug in the qemu/xen interface) makes it harder to refactor things later= on. Well, it's at least only a single concept, one that could even be used independently of Xen issues, while it appears to me like the other proposal comes with multiple ones. Jan --------------enigA286793C49D7C06177BA9609 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8G54wACgkQitSsb3rl5xQNmgCbBoh2+6C+sQ3RB1ZV4a9TB7bR SoYAn3t2QPxuja5CqwHVHmrgFW3CBu1w =wu1y -----END PGP SIGNATURE----- --------------enigA286793C49D7C06177BA9609--