From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [RFC][PATCH 14/16] kvm: x86: Add user space part for in-kernel i8259 Date: Mon, 05 Dec 2011 12:37:37 +0100 Message-ID: <4EDCAD01.2010608@web.de> References: <4EDB762C.7090909@redhat.com> <4EDB78DE.6000109@web.de> <4EDB7A74.4060804@redhat.com> <4EDB7ADC.50906@web.de> <4EDB7DE2.2050301@redhat.com> <4EDB7E62.7090909@web.de> <4EDB8DDE.5040402@redhat.com> <4EDB8F7C.1070602@web.de> <4EDBA15E.3060309@redhat.com> <4EDBE865.6000907@web.de> <4EDC9680.2070305@redhat.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigDE954290494DCF008F7F5DF0" Cc: Anthony Liguori , kvm@vger.kernel.org, "Michael S. Tsirkin" , Marcelo Tosatti , qemu-devel , Blue Swirl To: Avi Kivity Return-path: In-Reply-To: <4EDC9680.2070305@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigDE954290494DCF008F7F5DF0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 2011-12-05 11:01, Avi Kivity wrote: > On 12/04/2011 11:38 PM, Jan Kiszka wrote: >>> >>> It should be also possible to migrate from non-KVM device to KVM >>> version, different names would prevent that for ever. >> >> It is (theoretically) possible with these patches as the vmstate names= >> are the same. KVM to TCG migration does not work right now, so I was >> only able to test in-kernel <-> user space irqchip model migrations. >=20 > btw, for the next-gen migration protocol, we'd probably be using QOM > paths, not vmstate names; the QOM paths would include the device name? That would be a very bad idea IMHO. Every refactoring of your device tree, e.g. to model CPU hotplug and the ICC bus more accurately, would risk to create a migration crack. At least we would need some stable naming and/or alias concept then. Jan --------------enigDE954290494DCF008F7F5DF0 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.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7crQEACgkQitSsb3rl5xT5jACfc6Wp2PgWCGXQ5kA8iVzLfAiZ PvkAnjp1AQJNDV3BT9VD+JVUGjFi59xP =A7C/ -----END PGP SIGNATURE----- --------------enigDE954290494DCF008F7F5DF0-- From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:49596) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RXWri-0000kJ-95 for qemu-devel@nongnu.org; Mon, 05 Dec 2011 06:37:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RXWrg-0007N3-VH for qemu-devel@nongnu.org; Mon, 05 Dec 2011 06:37:46 -0500 Received: from fmmailgate03.web.de ([217.72.192.234]:54586) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RXWrg-0007Mn-C8 for qemu-devel@nongnu.org; Mon, 05 Dec 2011 06:37:44 -0500 Received: from moweb002.kundenserver.de (moweb002.kundenserver.de [172.19.20.108]) by fmmailgate03.web.de (Postfix) with ESMTP id B135E1AB39D33 for ; Mon, 5 Dec 2011 12:37:41 +0100 (CET) Message-ID: <4EDCAD01.2010608@web.de> Date: Mon, 05 Dec 2011 12:37:37 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <4EDB762C.7090909@redhat.com> <4EDB78DE.6000109@web.de> <4EDB7A74.4060804@redhat.com> <4EDB7ADC.50906@web.de> <4EDB7DE2.2050301@redhat.com> <4EDB7E62.7090909@web.de> <4EDB8DDE.5040402@redhat.com> <4EDB8F7C.1070602@web.de> <4EDBA15E.3060309@redhat.com> <4EDBE865.6000907@web.de> <4EDC9680.2070305@redhat.com> In-Reply-To: <4EDC9680.2070305@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigDE954290494DCF008F7F5DF0" Subject: Re: [Qemu-devel] [RFC][PATCH 14/16] kvm: x86: Add user space part for in-kernel i8259 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Anthony Liguori , kvm@vger.kernel.org, "Michael S. Tsirkin" , Marcelo Tosatti , qemu-devel , Blue Swirl This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigDE954290494DCF008F7F5DF0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 2011-12-05 11:01, Avi Kivity wrote: > On 12/04/2011 11:38 PM, Jan Kiszka wrote: >>> >>> It should be also possible to migrate from non-KVM device to KVM >>> version, different names would prevent that for ever. >> >> It is (theoretically) possible with these patches as the vmstate names= >> are the same. KVM to TCG migration does not work right now, so I was >> only able to test in-kernel <-> user space irqchip model migrations. >=20 > btw, for the next-gen migration protocol, we'd probably be using QOM > paths, not vmstate names; the QOM paths would include the device name? That would be a very bad idea IMHO. Every refactoring of your device tree, e.g. to model CPU hotplug and the ICC bus more accurately, would risk to create a migration crack. At least we would need some stable naming and/or alias concept then. Jan --------------enigDE954290494DCF008F7F5DF0 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.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7crQEACgkQitSsb3rl5xT5jACfc6Wp2PgWCGXQ5kA8iVzLfAiZ PvkAnjp1AQJNDV3BT9VD+JVUGjFi59xP =A7C/ -----END PGP SIGNATURE----- --------------enigDE954290494DCF008F7F5DF0--