From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MDEyb-0000gP-7E for qemu-devel@nongnu.org; Sun, 07 Jun 2009 05:47:41 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MDEyW-0000fS-8k for qemu-devel@nongnu.org; Sun, 07 Jun 2009 05:47:40 -0400 Received: from [199.232.76.173] (port=59930 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MDEyW-0000fM-0H for qemu-devel@nongnu.org; Sun, 07 Jun 2009 05:47:36 -0400 Received: from fmmailgate01.web.de ([217.72.192.221]:54684) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MDEyV-0004o3-BL for qemu-devel@nongnu.org; Sun, 07 Jun 2009 05:47:35 -0400 Message-ID: <4A2B8CB5.9040403@web.de> Date: Sun, 07 Jun 2009 11:47:33 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <4A26F1E3.1040509@codemonkey.ws> <4A2A92FE.2010700@redhat.com> <4A2AA10B.6060401@web.de> <4A2B49C0.8020703@redhat.com> <4A2B6DD8.3090104@web.de> <4A2B7F5E.8050807@web.de> <4A2B8787.5080603@web.de> <4A2B8A4D.3010703@redhat.com> In-Reply-To: <4A2B8A4D.3010703@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig1EE9698E5446F12CC5DD3DD0" Sender: jan.kiszka@web.de Subject: [Qemu-devel] Re: POLL: Why do you use kqemu? List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Blue Swirl , =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= , "qemu-devel@nongnu.org" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig1EE9698E5446F12CC5DD3DD0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Avi Kivity wrote: > Jan Kiszka wrote: >>>> >>>> Check e.g the diff of hw/vga.c against upstream: All the magic dance= s >>>> there are required as qemu-kvm tracking >>>> cpu_register_physical_memory and >>>> kvm_log_start cannot cope with all the patterns normal qemu code co= mes >>>> up with. Upstream slot management now provides the same features >>>> (including migration) like qemu-kvm, it just does not deal with >>>> legacy, >>>> thus it does not have to patch qemu code (rather, we were able to >>>> remove >>>> some already merged hooks - vga_dirty_log_stop). >>>> =20 >>> Still not very restrictive, all this could be encapsulated with for >>> example macro COMPAT_NO_DMRW which could be removed when we don't car= e >>> anymore. Next? >>> =20 >> >> Really, it's not worth the maintenance pain: Every new device emulatio= n >> code that wants to be KVM-legacy-compatible would need to be written >> like that. And unless you are familiar with the slot management >> internals, the "correct" pattern will not be obvious. >> =20 >=20 > Only devices which direct map memory. Currently VGA and cirrus. >=20 --- /data/qemu/hw/piix_pci.c 2009-06-07 09:42:27.000000000 +0200 +++ hw/piix_pci.c 2009-06-02 13:00:09.000000000 +0200 =2E.. @@ -91,6 +93,10 @@ static void i440fx_update_memory_mapping int i, r; uint32_t smram, addr; + if (kvm_enabled()) { + /* FIXME: Support remappings and protection changes. */ + return; + } update_pam(d, 0xf0000, 0x100000, (d->config[0x59] >> 4) & 3); for(i =3D 0; i < 12; i++) { r =3D (d->config[(i >> 1) + 0x5a] >> ((i & 1) * 4)) & 3; IIRC, this is at least partially due to the restricted slot management in qemu-kvm - or is this obsolete now? Jan --------------enig1EE9698E5446F12CC5DD3DD0 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.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkorjLUACgkQniDOoMHTA+laggCfTX97xjssNTMlJ6WinIIgxz9A YrIAniKg1fYOTsvL839nM5m1jy1IeP4o =1LjP -----END PGP SIGNATURE----- --------------enig1EE9698E5446F12CC5DD3DD0--