From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nujq5-0006MX-9F for qemu-devel@nongnu.org; Thu, 25 Mar 2010 05:58:57 -0400 Received: from [140.186.70.92] (port=53955 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nujq3-0006M1-7G for qemu-devel@nongnu.org; Thu, 25 Mar 2010 05:58:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Nujq1-000482-Bw for qemu-devel@nongnu.org; Thu, 25 Mar 2010 05:58:55 -0400 Received: from fmmailgate03.web.de ([217.72.192.234]:58805) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Nujq0-00047q-RE for qemu-devel@nongnu.org; Thu, 25 Mar 2010 05:58:53 -0400 Message-ID: <4BAB2F6B.5010400@web.de> Date: Thu, 25 Mar 2010 10:39:55 +0100 From: Jan Kiszka MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: KVM call agenda for Mar 23 References: <20100323061140.GN29498@x200.localdomain> <4BA88A6F.2050703@web.de> <4BA88F5D.6040008@redhat.com> <4BA8B7FB.2050103@codemonkey.ws> <4BA8BA84.3020908@redhat.com> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig538FD7CBF015ACFBEF3EB9A6" Sender: jan.kiszka@web.de List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Zhang, Xiantao" Cc: Chris Wright , "kvm@vger.kernel.org" , Jes Sorensen , "qemu-devel@nongnu.org" , Avi Kivity This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig538FD7CBF015ACFBEF3EB9A6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Zhang, Xiantao wrote: > Jes Sorensen wrote: >> On 03/23/10 13:45, Anthony Liguori wrote: >>> I don't think we can pull in: >>> >>> - extboot >>> - ia64 >>> - in-kernel pit[1] >>> - associated command line options >>> - device passthrough >>> >>> The question is, if we dropped those things, would people actually >>> use qemu.git instead of qemu-kvm.git. If the answer is "no", what >>> set of things do we need in order for people to focus on qemu.git >>> instead of qemu-kvm.git. >> I am not sure if anyone is still actively working on ia64. According >> to the qemu-kvm.git logs, there hasn't been any real ia64 changes to >> the code since my last commit in June of last year and then a couple >> of minor configure bits. >> >> IMHO we can just let it rot - not sure if Xiantao is still interested?= > For ia64 part, maybe we can keep the current qemu-kvm.git for the users= =2E And it is not a must to push it into Qemu upstream.=20 > Xiantao >=20 Does it still build & work? Does someone test it at least infrequently? Or are there users? There were a few changes recently due to cleanups and/or switches to upstream code. There will be more in the future. And at some point heavy work will be needed when there are no more qemu-kvm* files. That could be a point ia64 breaks forever unless someone jumps in. BTW, I'm also carrying ia64 bits in kvm-kmod. I never compiled them (except for the "make headers_install" which throws tons of warnings at me), I'm just keeping them for now to enforce architecture separation in case someone once wishes to add another arch to this wrapper. Jan --------------enig538FD7CBF015ACFBEF3EB9A6 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 iEYEARECAAYFAkurL3EACgkQitSsb3rl5xQhggCgyodihqxamkHGUp5bJr+9aArg pAYAnjs8ghQQ1w12Vapv+dcGSBY/TaLk =dwiJ -----END PGP SIGNATURE----- --------------enig538FD7CBF015ACFBEF3EB9A6--