From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Nu3f9-0007HQ-39
	for qemu-devel@nongnu.org; Tue, 23 Mar 2010 08:56:51 -0400
Received: from [199.232.76.173] (port=38727 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Nu3f7-0007H3-No
	for qemu-devel@nongnu.org; Tue, 23 Mar 2010 08:56:49 -0400
Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim
	4.60) (envelope-from <Jes.Sorensen@redhat.com>) id 1Nu3f6-0004hv-M4
	for qemu-devel@nongnu.org; Tue, 23 Mar 2010 08:56:49 -0400
Received: from mx1.redhat.com ([209.132.183.28]:2106)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <Jes.Sorensen@redhat.com>) id 1Nu3f6-0004hh-83
	for qemu-devel@nongnu.org; Tue, 23 Mar 2010 08:56:48 -0400
Message-ID: <4BA8BA84.3020908@redhat.com>
Date: Tue, 23 Mar 2010 13:56:36 +0100
From: Jes Sorensen <Jes.Sorensen@redhat.com>
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>
In-Reply-To: <4BA8B7FB.2050103@codemonkey.ws>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Chris Wright <chrisw@redhat.com>, kvm@vger.kernel.org, qemu-devel@nongnu.org, Jan Kiszka <jan.kiszka@web.de>, Avi Kivity <avi@redhat.com>

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?

Cheers,
Jes