From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: KVM call agenda for Mar 23 Date: Tue, 23 Mar 2010 11:50:49 +0100 Message-ID: <4BA89D09.8040700@web.de> References: <20100323061140.GN29498@x200.localdomain> <4BA88A6F.2050703@web.de> <4BA88F5D.6040008@redhat.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig2E04D31F2DF7AEFCBC896BAE" Cc: Chris Wright , kvm@vger.kernel.org, qemu-devel@nongnu.org To: Avi Kivity Return-path: Received: from fmmailgate01.web.de ([217.72.192.221]:46118 "EHLO fmmailgate01.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751835Ab0CWKu7 (ORCPT ); Tue, 23 Mar 2010 06:50:59 -0400 In-Reply-To: <4BA88F5D.6040008@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig2E04D31F2DF7AEFCBC896BAE Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Avi Kivity wrote: > On 03/23/2010 11:31 AM, Jan Kiszka wrote: >> 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 >=20 > - alternative path of merging qemu-kvm.git's implementation as is and > cleaning it up in qemu.git. >=20 > 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... 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. Jan --------------enig2E04D31F2DF7AEFCBC896BAE 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 iEYEARECAAYFAkuonREACgkQitSsb3rl5xREawCgq+iid2oqE6WNlkOgTzJ3dfc2 WG0AoLUaATAlsPKeYy4p9YKmP1bcHwpd =nYaH -----END PGP SIGNATURE----- --------------enig2E04D31F2DF7AEFCBC896BAE--