From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nu23X-0002Ab-MU for qemu-devel@nongnu.org; Tue, 23 Mar 2010 07:13:55 -0400 Received: from [199.232.76.173] (port=45202 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nu23W-00028m-MO for qemu-devel@nongnu.org; Tue, 23 Mar 2010 07:13:54 -0400 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1Nu23U-0007M4-VP for qemu-devel@nongnu.org; Tue, 23 Mar 2010 07:13:54 -0400 Received: from fmmailgate02.web.de ([217.72.192.227]:55348) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Nu23U-0007Lw-F0 for qemu-devel@nongnu.org; Tue, 23 Mar 2010 07:13:52 -0400 Message-ID: <4BA8A26E.2070403@web.de> Date: Tue, 23 Mar 2010 12:13:50 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <20100323061140.GN29498@x200.localdomain> <4BA88A6F.2050703@web.de> <4BA88F5D.6040008@redhat.com> <4BA89D09.8040700@web.de> <4BA89E7F.2010200@redhat.com> In-Reply-To: <4BA89E7F.2010200@redhat.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig10ACC51DD92060D0B0D8B862" Sender: jan.kiszka@web.de Subject: [Qemu-devel] Re: KVM call agenda for Mar 23 List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Chris Wright , qemu-devel@nongnu.org, kvm@vger.kernel.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig10ACC51DD92060D0B0D8B862 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Avi Kivity wrote: > On 03/23/2010 12:50 PM, Jan Kiszka wrote: >> Avi Kivity wrote: >> =20 >>> On 03/23/2010 11:31 AM, Jan Kiszka wrote: >>> =20 >>>> Chris Wright wrote: >>>> >>>> =20 >>>>> Please send in any agenda items you are interested in covering. >>>>> >>>>> Yes, usability is a valid topic esp. if you promise to come w/ GUI >>>>> patches. >>>>> >>>>> >>>>> =20 >>>> - state and roadmap for upstream merge of in-kernel device models >>>> (looks to me like this central merge effort is stalled ATM) >>>> >>>> =20 >>> - alternative path of merging qemu-kvm.git's implementation as is and= >>> cleaning it up in qemu.git. >>> >>> For kvm.git, I wouldn't dream of merging something with outstanding >>> issues and cleaning them up "later", but the situation is somewhat >>> different with qemu vs qemu-kvm. >>> >>> =20 >> So the benefit would be less merge conflicts/regressions on >> qemu-kvm.git? But you may break non-x86 KVM support in upstream as it >> already uses the cleaned up kvm subsystem. /me is not immediately >> convinced... >> =20 >=20 > The benefit would be that qemu-kvm.git would become a staging tree > instead of the master repository for kvm users. As an example, we > wouldn't have any bisectability problems. kvm features would need to b= e > written just once. >=20 The last item would imply throwing away what qemu.git already cleaned up - or finally convert the rest. There is no lazy path. >=20 >> We are more than half-way through this, so let's focus efforts for the= >> last bits that make the difference widely negligible. This investment >> should pay off rather quickly. >> =20 >=20 > If we merge now, we merge the half-completed effort so we don't lose > anything. However, if we can complete the merge quickly, I'm all for > it. I don't want to introduce the ugliness into qemu.git any more than= > you do. One issue of merging blindly is the command line option zoo of qemu-kvm. I don't think we want this upstream first and then deprecate it quickly again. >=20 > Note, the above discussion ignores extboot and device assignment, but > let's focus on the thorny bits first. >=20 I don't think extboot will make it upstream anymore, now that there is an effort for a gpxe-based virtio boot loader. Jan --------------enig10ACC51DD92060D0B0D8B862 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 iEYEARECAAYFAkuoom4ACgkQitSsb3rl5xT9MwCgo+8W6uQ4+0ogEJ/LtF8CM1yZ DZQAn2AygEvZVIiwoCYy5qRQzl2QKSbj =MdMm -----END PGP SIGNATURE----- --------------enig10ACC51DD92060D0B0D8B862--